Triple
T34827081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collooney |
E1003953
|
entity |
| Predicate | hasHistoricTransportRole |
P199017
|
FINISHED |
| Object | railway junction on the Midland Great Western Railway |
—
|
LITERAL 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: railway junction on the Midland Great Western Railway | Statement: [Collooney, hasHistoricTransportRole, railway junction on the Midland Great Western Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricTransportRole Context triple: [Collooney, hasHistoricTransportRole, railway junction on the Midland Great Western Railway]
-
A.
transportHistoryRole
Indicates the specific function or capacity an entity had within a particular transport event or transport-related history.
-
B.
hasHistoricalRoleAs
Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or context.
-
C.
historicalTransportRole
chosen
Indicates that an entity served as a means or facilitator of transportation in a past historical context.
-
D.
hasTransportHistoryAs
Indicates that an entity has a record or log of being transported, characterized or classified in a specific way.
-
E.
hasTransportHistory
Indicates that there exists a record or sequence of past transportation-related events or movements associated with an entity.
- 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_69f76db7d1b4819093bd4912d80d845d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4 p.m.