Triple
T29459382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weardale Railway |
E747189
|
entity |
| Predicate | primaryHistoricFreight |
P127465
|
FINISHED |
| Object | limestone |
—
|
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: limestone | Statement: [Weardale Railway, primaryHistoricFreight, limestone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryHistoricFreight Context triple: [Weardale Railway, primaryHistoricFreight, limestone]
-
A.
formerRailUse
Indicates that an entity previously served a particular railway-related function or purpose, but no longer does so.
-
B.
hasFreightHistory
chosen
Indicates that an entity has a recorded history of freight-related activities, such as shipments or cargo movements, associated with it.
-
C.
historicalTransportRole
Indicates that an entity served as a means or facilitator of transportation in a past historical context.
-
D.
hasRailroadHistoryWith
Indicates a historical relationship or connection between entities involving railroads, such as shared development, operation, or significant events in railway history.
-
E.
hasPrimaryUseHistoric
Indicates that something is primarily used for historic or heritage-related purposes.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a0136e4af808190b529d324bbf0c5d9 |
completed | May 11, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_6a01369141c4819091cb8064913a44ca |
completed | May 11, 2026, 1:53 a.m. |
Created at: April 28, 2026, 3:48 p.m.