Triple
T30927579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athboy |
E787899
|
entity |
| Predicate | isServedByBus |
P39381
|
FINISHED |
| Object | Bus Éireann services |
E1095406
|
NE 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: Bus Éireann services | Statement: [Athboy, isServedByBus, Bus Éireann services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isServedByBus Context triple: [Athboy, isServedByBus, Bus Éireann services]
-
A.
isPublicTransport
Indicates that the entity functions as a mode or instance of transportation that is available for use by the general public, typically operating on fixed routes or schedules.
-
B.
hasBusServices
chosen
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
C.
isPublicTransportRoute
Indicates that a given route is designated and operated as part of a public transportation system available for general use.
-
D.
hasPublicTransitRoute
Indicates that there exists a public transportation route (such as a bus, train, or tram line) connecting or serving the related entities.
-
E.
hasNightBusService
Indicates that a transportation route or stop is served by buses operating during nighttime hours.
- F. None of above.
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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28e46f62388190a7cc137d957d2d89 |
completed | June 10, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:51 p.m.