Triple
T31999332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antrim railway station |
E817079
|
entity |
| Predicate | usesRailOperatorBrand |
P39149
|
FINISHED |
| Object | Translink |
—
|
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: Translink | Statement: [Antrim railway station, usesRailOperatorBrand, Translink]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRailOperatorBrand Context triple: [Antrim railway station, usesRailOperatorBrand, Translink]
-
A.
railwayOperatorBranding
chosen
Indicates that one entity is responsible for the railway-related branding, livery, or visual identity applied to another entity (such as a train service, station, or rolling stock).
-
B.
usesRollingStockBrand
Indicates that one entity employs or operates rolling stock manufactured under a specific brand.
-
C.
hasRailOperatorNamedAfter
Indicates that a rail operator is named after the specified entity.
-
D.
hasRailTransportOperator
Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
-
E.
hasLocalRailOperator
Indicates that a specified rail operator is responsible for providing local or regional rail services within a particular area or network.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: May 1, 2026, 12:14 a.m.