Triple
T35020720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose (Doctor Who) |
E1010186
|
entity |
| Predicate | endSceneElement |
P38927
|
FINISHED |
| Object | Doctor invites Rose to travel in TARDIS |
—
|
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: Doctor invites Rose to travel in TARDIS | Statement: [Rose (Doctor Who), endSceneElement, Doctor invites Rose to travel in TARDIS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endSceneElement Context triple: [Rose (Doctor Who), endSceneElement, Doctor invites Rose to travel in TARDIS]
-
A.
dropElement
Indicates that an element is removed or discarded from a collection, sequence, or structure.
-
B.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
-
C.
finalSceneAction
chosen
Indicates the action or event that occurs in the concluding or final scene of a narrative or sequence.
-
D.
endUseEvent
Indicates an event marking the final or terminating use of something by an entity.
-
E.
endOfState
Indicates the point or condition at which a particular state, situation, or process comes to an end.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.