Triple
T37354972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Move that bus" home reveal |
E927429
|
entity |
| Predicate | takesPlaceAtEndOf |
P48547
|
FINISHED |
| Object | episode |
—
|
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: episode | Statement: ["Move that bus" home reveal, takesPlaceAtEndOf, episode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takesPlaceAtEndOf Context triple: ["Move that bus" home reveal, takesPlaceAtEndOf, episode]
-
A.
isUsuallyTakenAtEndOf
Indicates that one event, action, or item typically occurs or is taken after the completion of another.
-
B.
endOf
chosen
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
C.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
D.
canEndOn
Indicates that one entity is allowed or able to terminate, conclude, or finish with another specified entity or condition.
-
E.
concludesIn
Indicates that an event, process, or action ends or reaches its final state within a specified time, place, or context.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:16 p.m.