Triple
T29931559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Youth (Passing Strange) |
E760226
|
entity |
| Predicate | appearsWithNarrator |
P159728
|
FINISHED |
| Object | Narrator (Passing Strange) |
—
|
NE NERFINISHED |
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: Narrator (Passing Strange) | Statement: [Youth (Passing Strange), appearsWithNarrator, Narrator (Passing Strange)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsWithNarrator Context triple: [Youth (Passing Strange), appearsWithNarrator, Narrator (Passing Strange)]
-
A.
hasCoNarrator
Indicates that two or more entities share the role of narrating the same work, event, or story together.
-
B.
narratesWith
chosen
Indicates that one entity tells, recounts, or presents a story, event, or information in conjunction with or alongside another entity.
-
C.
narratorOf
Indicates that one entity serves as the narrator or storytelling voice for another entity, such as a text, story, or media work.
-
D.
hasNarration
Indicates that an entity provides spoken or written commentary or storytelling for another entity, such as a work, event, or scene.
-
E.
narratorType
Indicates the narrative perspective or role from which a story or account is being told.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 29, 2026, 6:18 p.m.