Triple
T18107492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mississippi River system locks and dams |
E433381
|
entity |
| Predicate | typicalLockChamberLength |
P51573
|
FINISHED |
| Object | 600 feet |
—
|
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: 600 feet | Statement: [Mississippi River system locks and dams, typicalLockChamberLength, 600 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLockChamberLength Context triple: [Mississippi River system locks and dams, typicalLockChamberLength, 600 feet]
-
A.
hasChamberLength
chosen
Indicates the length measurement of a chamber associated with an entity.
-
B.
hasChamberWidth
Indicates that an entity possesses a chamber whose width has a specified value or range.
-
C.
hasChamberStructure
Indicates that an entity possesses a specific internal chamber or compartmentalized structural organization.
-
D.
hasChamberSize
Indicates a relationship where an entity is associated with, or characterized by, a specific size of a chamber or internal compartment.
-
E.
maximumChamberHeight
Indicates the greatest vertical distance from the lowest to the highest point within a specified chamber.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddbb3d408190b5fc7870bc6512f4 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.