Triple
T35211405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leicester Ring |
E1016688
|
entity |
| Predicate | hasLockFlights |
P59549
|
FINISHED |
| Object | Foxton Locks |
—
|
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: Foxton Locks | Statement: [Leicester Ring, hasLockFlights, Foxton Locks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLockFlights Context triple: [Leicester Ring, hasLockFlights, Foxton Locks]
-
A.
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.
-
B.
hasScheduledFlights
Indicates that there are one or more flights planned and set to occur between the related entities according to a schedule.
-
C.
numberOfLocksInMainFlight
Indicates the total count of locks present in the main flight (primary sequence) of a canal or lock system.
-
D.
hasNoScheduledFlights
Indicates that there are currently zero flights planned or scheduled for the given entity (such as a route, airport, or airline) within the relevant time frame.
-
E.
isFlownWith
Indicates that one entity travels by air together with, or using the same flight as, another 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff14d596e88190be5263b7f96a96cd |
completed | May 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69ff13f0208081909369aeb3b77a6b1f |
completed | May 9, 2026, 11:01 a.m. |
Created at: May 3, 2026, 4:02 p.m.