Triple
T5341405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buras-Triumph, Louisiana |
E123951
|
entity |
| Predicate | coastalCommunity |
P21854
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Buras-Triumph, Louisiana, coastalCommunity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalCommunity Context triple: [Buras-Triumph, Louisiana, coastalCommunity, true]
-
A.
isCoastalCommunity
chosen
Indicates that a community is located along a coast or shoreline and is directly associated with a nearby sea or ocean.
-
B.
coastalInteraction
Indicates an interaction or relationship occurring between entities and a coastal environment, such as along shorelines or near the sea.
-
C.
coastalCluster
Indicates a grouping of entities that are located near or along the same coastal area or shoreline.
-
D.
includesCoastalTown
Indicates that a geographic area or region contains at least one town located on or directly adjacent to a coastline.
-
E.
hasCoastalEnvironment
Indicates that an entity is located in, adjacent to, or characterized by a coastal environment or shoreline setting.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85e86edc81908d87933db6489f91 |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845a62b081909782863865b257a9 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.