Triple
T4711731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridgnorth Cliff Railway |
E104526
|
entity |
| Predicate | laterPropulsion |
P59116
|
FINISHED |
| Object | electric haulage system |
—
|
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: electric haulage system | Statement: [Bridgnorth Cliff Railway, laterPropulsion, electric haulage system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPropulsion Context triple: [Bridgnorth Cliff Railway, laterPropulsion, electric haulage system]
-
A.
originalPropulsion
Indicates that one entity serves as the initial or native means of propulsion or movement for another entity.
-
B.
propulsion
Indicates a relationship where one entity provides the driving force or thrust that moves another entity forward or keeps it in motion.
-
C.
propulsionFeature
Indicates a relationship where a propulsion-related characteristic or capability is attributed to an entity.
-
D.
propulsionMedium
Indicates the medium or substance through which propulsion is generated or transmitted for movement.
-
E.
propulsionCycle
Indicates the type or pattern of propulsion operation or cycle that characterizes how a system generates and sustains thrust or movement.
- F. None of above. chosen
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_69bd43eac3c08190af7e4020c6c3704c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd680b06e881908de87edf815f3cc0 |
completed | March 20, 2026, 3:30 p.m. |
Created at: March 20, 2026, 1:17 p.m.