Triple
T32565003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mississippi River at New Orleans |
E832336
|
entity |
| Predicate | hasNavigationProjectDepth |
P188408
|
FINISHED |
| Object | approximately 50 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: approximately 50 feet | Statement: [Mississippi River at New Orleans, hasNavigationProjectDepth, approximately 50 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavigationProjectDepth Context triple: [Mississippi River at New Orleans, hasNavigationProjectDepth, approximately 50 feet]
-
A.
navigationalDepth
chosen
Indicates the depth of water available or required for safe navigation along a particular route or at a specific location.
-
B.
hasDepth
Indicates that an entity possesses a measurable extent or distance from its surface inward or from top to bottom.
-
C.
hierarchyDepth
Indicates the level or distance of an entity from the top (root) within a hierarchical structure.
-
D.
hasNavigationSpan
Indicates that one entity includes or is associated with a specific navigational range or segment used for movement or routing.
-
E.
hasApproximateDepth
Indicates that an entity is associated with a depth value that is not exact but estimated or approximate.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: May 1, 2026, 1:03 a.m.