Triple
T38130833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of South Louisiana |
E952216
|
entity |
| Predicate | stretchFrom |
P122441
|
FINISHED |
| Object | New Orleans, Louisiana |
—
|
NE NERFINISHED |
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: New Orleans, Louisiana | Statement: [Port of South Louisiana, stretchFrom, New Orleans, Louisiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stretchFrom Context triple: [Port of South Louisiana, stretchFrom, New Orleans, Louisiana]
-
A.
stretchedFrom
chosen
Indicates that one entity extends or reaches out in space or time starting at another specified entity or point.
-
B.
isStretchOf
Indicates that one linear feature (such as a road, river, or path) constitutes a continuous segment or portion of another, longer linear feature.
-
C.
frontStretchLength
Indicates the measured length of the front stretch portion of something (such as a track, course, or path).
-
D.
extendedTowards
Indicates that one entity is stretched or directed outward in the direction of another entity or location.
-
E.
extendedFrom
Indicates that one entity is derived by adding to or building upon the scope, content, or structure of another entity.
- 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_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.