Triple
T31515538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owen Warland |
E804063
|
entity |
| Predicate | isMisunderstoodBy |
P38994
|
FINISHED |
| Object | practical society |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: practical society | Statement: [Owen Warland, isMisunderstoodBy, practical society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMisunderstoodBy Context triple: [Owen Warland, isMisunderstoodBy, practical society]
-
A.
misinterpretedBy
chosen
Indicates that something (such as a statement, action, or signal) is understood incorrectly or in a way not intended by a particular entity.
-
B.
betterUnderstoodAs
Indicates that one concept, term, or representation is more accurately or clearly interpreted when viewed as another specified concept, term, or representation.
-
C.
notableMisconception
Indicates that a commonly held but incorrect belief or understanding exists about the subject.
-
D.
disputedInterpretation
Indicates that there is disagreement or contention over how something should be understood, interpreted, or explained.
-
E.
misrepresentedIn
Indicates that something is inaccurately or falsely portrayed within a particular source, context, or representation.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a2578cb081908304c8d338fb5b81 |
completed | May 3, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:52 p.m.