Triple
T8461984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allington Lock |
E200061
|
entity |
| Predicate | hasMaximumVesselType |
P2429
|
FINISHED |
| Object | inland waterway craft |
—
|
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: inland waterway craft | Statement: [Allington Lock, hasMaximumVesselType, inland waterway craft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumVesselType Context triple: [Allington Lock, hasMaximumVesselType, inland waterway craft]
-
A.
maximumVesselType
chosen
Indicates the highest or largest class, size, or category of vessel that is allowed, applicable, or associated in a given context.
-
B.
hasVesselType
Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
-
C.
maximumVesselLength
Indicates the greatest allowable or observed length of a vessel in a given context or constraint.
-
D.
usesVesselType
Indicates that an entity performs an activity or operation by employing a specific type or category of vessel.
-
E.
maxVesselTonnage
Indicates the maximum tonnage capacity that a vessel is allowed or designed to carry.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4a0ff4c8190b17bbd33db632cea |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.