Triple
T30236362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On the Buses |
E768777
|
entity |
| Predicate | hasDriverCharacter |
P118377
|
FINISHED |
| Object | Stan Butler |
—
|
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: Stan Butler | Statement: [On the Buses, hasDriverCharacter, Stan Butler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDriverCharacter Context triple: [On the Buses, hasDriverCharacter, Stan Butler]
-
A.
hasDriver
Indicates that an entity is operated, controlled, or driven by a specific person or agent.
-
B.
hasFictionalDriver
chosen
Indicates that an entity (such as a vehicle or object) is associated with a driver who is a fictional or imaginary character.
-
C.
hasDriverCategory
Indicates that an entity (such as a vehicle or driving role) is associated with a specific driver category or license class.
-
D.
hasPrimaryDriver
Indicates that an entity is designated as the main or principal driver responsible for operating another entity, typically a vehicle.
-
E.
drivingCharacter
Indicates that one character is operating or controlling a vehicle or mode of transportation.
- 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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 7:37 p.m.