Triple
T23372849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delight in Disorder |
E593519
|
entity |
| Predicate | poeticSpeaker |
P136313
|
FINISHED |
| Object | first-person observer |
—
|
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: first-person observer | Statement: [Delight in Disorder, poeticSpeaker, first-person observer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: poeticSpeaker Context triple: [Delight in Disorder, poeticSpeaker, first-person observer]
-
A.
hasPoeticSpeaker
chosen
Indicates that one entity functions as the poetic speaker or voice expressing the content of another entity (such as a poem or lyrical work).
-
B.
poet
Indicates that an entity creates poetry or is recognized for engaging in the activity of writing poems.
-
C.
hasPoeticVoice
Indicates that one entity possesses or exhibits the distinctive poetic style, tone, or expressive voice associated with another entity.
-
D.
favoritePoet
Indicates that one entity is the poet whom another entity prefers above all other poets.
-
E.
characterizesPoetAs
Indicates that one entity portrays, defines, or describes a poet in terms of particular qualities, roles, or attributes.
- 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3b0bc3c8190b1093f7ea29d015c |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:33 p.m.