Triple
T36414253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertford Union Canal |
E896961
|
entity |
| Predicate | lockFlightLocation |
P59549
|
FINISHED |
| Object | Old Ford |
—
|
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: Old Ford | Statement: [Hertford Union Canal, lockFlightLocation, Old Ford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lockFlightLocation Context triple: [Hertford Union Canal, lockFlightLocation, Old Ford]
-
A.
lockFlightName
Indicates that a specific flight’s name or identifier is fixed and cannot be changed.
-
B.
hasLockFlight
chosen
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.
testFlightLocation
Indicates the location where a test flight takes place or is conducted.
-
D.
lockFlightOrientation
Indicates that an entity constrains or fixes another entity’s flight orientation so it cannot freely change its attitude or direction.
-
E.
positionOnFlight
Indicates the specific seat or positional assignment that an entity has on a particular flight.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.