Triple
T30236363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On the Buses |
E768777
|
entity |
| Predicate | hasConductorCharacter |
P203092
|
FINISHED |
| Object | Jack Harper |
—
|
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: Jack Harper | Statement: [On the Buses, hasConductorCharacter, Jack Harper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConductorCharacter Context triple: [On the Buses, hasConductorCharacter, Jack Harper]
-
A.
hasConductor
Indicates that an entity (such as an event, performance, or ensemble) is associated with a specific conductor who leads or directs it.
-
B.
hasConductorDependingOn
Indicates that one entity has a conductor whose role, presence, or characteristics depend on another specified entity or condition.
-
C.
hasNoPrincipalConductor
Indicates that an entity, such as an orchestra or ensemble, does not have a designated principal conductor in charge of its musical direction.
-
D.
conductorType
Indicates the type or category of conductor involved in the relationship or action (e.g., material, role, or functional class).
-
E.
principalConductor
Indicates that one entity serves as the main or lead conductor for another entity, typically an orchestra or musical ensemble.
- 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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a011ee3507081908b42de4278ae0b83 |
completed | May 11, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_6a011e874420819091cac3f08e8aa3f9 |
completed | May 11, 2026, 12:10 a.m. |
| PDg | Predicate description generation | batch_6a011ee2a6408190b3b2763d01bac623 |
completed | May 11, 2026, 12:12 a.m. |
Created at: April 29, 2026, 7:37 p.m.