Triple
T34430867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Córas Iompair Éireann |
E883822
|
entity |
| Predicate | urbanBusOperator |
P73415
|
FINISHED |
| Object | Dublin Bus |
—
|
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: Dublin Bus | Statement: [Córas Iompair Éireann, urbanBusOperator, Dublin Bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanBusOperator Context triple: [Córas Iompair Éireann, urbanBusOperator, Dublin Bus]
-
A.
providesUrbanTransport
chosen
Indicates that one entity supplies or operates transportation services within an urban or city environment for another entity or the public.
-
B.
publicTransportAuthority
Indicates that one entity serves as the governing or managing authority responsible for overseeing public transportation services related to another entity.
-
C.
accessByBusFrom
Indicates that one location can be reached from another location using a bus as the mode of transportation.
-
D.
tramOperator
Indicates that one entity operates, manages, or runs tram services for another entity or area.
-
E.
busSystemName
Indicates that a bus system is identified or referred to by a specific name.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f728a345488190bd7e6751b09ac591 |
completed | May 3, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69f7283ef2608190a7a85d7e7f5332c0 |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 2 a.m.