Triple
T10175481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thames and Severn Canal |
E235840
|
entity |
| Predicate | maximumBoatWidth |
P12550
|
FINISHED |
| Object | narrowboat gauge |
—
|
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: narrowboat gauge | Statement: [Thames and Severn Canal, maximumBoatWidth, narrowboat gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumBoatWidth Context triple: [Thames and Severn Canal, maximumBoatWidth, narrowboat gauge]
-
A.
maximumShipBeam
chosen
Indicates the greatest allowable or observed width of a ship across its widest point.
-
B.
hasBoatCapacity
Indicates the maximum number of people or amount of load that a boat is designed or allowed to carry.
-
C.
maximumVesselLength
Indicates the greatest allowable or observed length of a vessel in a given context or constraint.
-
D.
maximumVesselType
Indicates the highest or largest class, size, or category of vessel that is allowed, applicable, or associated in a given context.
-
E.
maximumChannelWidth
Indicates the greatest allowable or observed width of a channel in the given context.
- 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_69ca84d1d5f88190ab878a1021ecff68 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdecd26a8c8190a391b9d5e47ebb72 |
completed | April 2, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:11 p.m.