Triple
T36109984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain W. |
E1044466
|
entity |
| Predicate | narratesEventsLeadingTo |
P193280
|
FINISHED |
| Object | introduction of Peter Pan |
—
|
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: introduction of Peter Pan | Statement: [Captain W., narratesEventsLeadingTo, introduction of Peter Pan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narratesEventsLeadingTo Context triple: [Captain W., narratesEventsLeadingTo, introduction of Peter Pan]
-
A.
storylineEvent
Indicates that one event occurs as a distinct step or component within a larger narrative or storyline.
-
B.
narratesWith
Indicates that one entity tells, recounts, or presents a story, event, or information in conjunction with or alongside another entity.
-
C.
narrativeSequence
Indicates that one event or narrative element follows another in a temporal or logical storytelling order.
-
D.
hasNarrativeEvent
Indicates that one entity includes, contains, or is associated with a specific narrative event within a story or sequence of events.
-
E.
partOfSeriesOfEvents
Indicates that an event is one element within a larger, ordered sequence of related events.
- F. None of above. chosen
Provenance (4 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
| PDg | Predicate description generation | batch_69fd3d45ccb8819082f15e60bd33afc9 |
completed | May 8, 2026, 1:32 a.m. |
Created at: May 3, 2026, 4:08 p.m.