Triple
T13635731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stoke Bruerne Locks |
E325842
|
entity |
| Predicate | lockFlightOrientation |
P111401
|
FINISHED |
| Object | north-south |
—
|
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: north-south | Statement: [Stoke Bruerne Locks, lockFlightOrientation, north-south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lockFlightOrientation Context triple: [Stoke Bruerne Locks, lockFlightOrientation, north-south]
-
A.
controlsPhaseOfFlight
Indicates that one entity has authority over or manages a specific phase of another entity’s flight operation.
-
B.
hasLockFlight
Indicates that one entity is associated with a specific lock flight, representing a relationship where the entity uses, contains, or is located at that sequence of canal locks.
-
C.
lockFlightHeightDifference
Indicates that the vertical distance between flights is constrained to remain fixed or within a specified bound.
-
D.
lockFlightName
Indicates that a specific flight’s name or identifier is fixed and cannot be changed.
-
E.
supportsFlightMode
Indicates that an entity provides or is compatible with a flight mode feature or operation.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe85e1c4819095194f4b7f9f6118 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc6043e148190a2a25f929cfa35e5 |
completed | April 12, 2026, 4:19 p.m. |
Created at: April 9, 2026, 9:51 p.m.