Triple
T22096973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autherley Junction |
E546060
|
entity |
| Predicate | elevationDifferenceManagedBy |
P140793
|
FINISHED |
| Object | stop lock |
—
|
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: stop lock | Statement: [Autherley Junction, elevationDifferenceManagedBy, stop lock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationDifferenceManagedBy Context triple: [Autherley Junction, elevationDifferenceManagedBy, stop lock]
-
A.
elevationChangeManagedBy
chosen
Indicates that the responsibility for controlling, adjusting, or overseeing a change in elevation (such as height, altitude, or level) is assigned to a particular managing entity.
-
B.
elevationControlledBy
Indicates that the elevation or vertical position of one entity is regulated, adjusted, or maintained by another entity.
-
C.
elevationChange
Indicates a change in vertical position or altitude between two points or states.
-
D.
elevationType
Indicates the kind or classification of elevation associated with an entity, such as how its height or altitude is characterized.
-
E.
hasTypicalElevationRelativeTo
Indicates the usual height or altitude of one entity in comparison to a referenced baseline or other 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128ea00d48190b020aba80dcdbec9 |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.