Triple
T29459233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frosterley |
E747185
|
entity |
| Predicate | hasRailTransportHistory |
P19012
|
FINISHED |
| Object | Weardale Railway |
—
|
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: Weardale Railway | Statement: [Frosterley, hasRailTransportHistory, Weardale Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailTransportHistory Context triple: [Frosterley, hasRailTransportHistory, Weardale Railway]
-
A.
hasRailroadHistory
Indicates that an entity is associated with, involved in, or notable for historical events, operations, or developments related to railroads.
-
B.
hasRailroadHistoryWith
chosen
Indicates a historical relationship or connection between entities involving railroads, such as shared development, operation, or significant events in railway history.
-
C.
hasRailSystem
Indicates that an entity possesses or is served by a rail-based transportation system.
-
D.
isOnHistoricTransportCorridor
Indicates that something is located along or within a transportation route that has recognized historical significance.
-
E.
hasStreetcarHistory
Indicates that there is a historical association or past involvement with streetcars or streetcar systems.
- 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_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 28, 2026, 3:48 p.m.