Triple
T21493276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lanaye lock complex |
E530288
|
entity |
| Predicate | hasMaximumVesselBeam |
P12550
|
FINISHED |
| Object | approximately 25 metres |
—
|
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: approximately 25 metres | Statement: [Lanaye lock complex, hasMaximumVesselBeam, approximately 25 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumVesselBeam Context triple: [Lanaye lock complex, hasMaximumVesselBeam, approximately 25 metres]
-
A.
maximumVesselLength
Indicates the greatest allowable or observed length of a vessel in a given context or constraint.
-
B.
maximumShipBeam
chosen
Indicates the greatest allowable or observed width of a ship across its widest point.
-
C.
maximumVesselType
Indicates the highest or largest class, size, or category of vessel that is allowed, applicable, or associated in a given context.
-
D.
maxVesselTonnage
Indicates the maximum tonnage capacity that a vessel is allowed or designed to carry.
-
E.
maximumVesselDraft
Indicates the greatest depth a vessel can safely extend below the waterline, typically limiting where it can navigate or dock.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea54fb608190a147cd8aa6d6d04b |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:23 p.m.