Triple
T38130832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of South Louisiana |
E952216
|
entity |
| Predicate | hasWaterwayLength |
P59548
|
FINISHED |
| Object | approximately 54 miles |
—
|
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 54 miles | Statement: [Port of South Louisiana, hasWaterwayLength, approximately 54 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterwayLength Context triple: [Port of South Louisiana, hasWaterwayLength, approximately 54 miles]
-
A.
waterwayLengthKilometres
chosen
Indicates the total length of a waterway, measured in kilometres.
-
B.
waterwayWidth
Indicates the measured width of a waterway, typically the distance across it from one bank or edge to the opposite.
-
C.
riverLength
Indicates the measured extent of a river from its source to its mouth, typically expressed as a linear distance.
-
D.
riverLengthContext
Indicates the contextual or situational information under which a river’s length is measured or considered.
-
E.
lengthOverWater
Indicates the portion of an object’s total length that lies over water rather than over land or other surfaces.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:21 p.m.