Triple
T27026580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastpoint, Franklin County, Florida |
E680803
|
entity |
| Predicate | coastalCommunityOf |
P21854
|
FINISHED |
| Object | Gulf of Mexico |
—
|
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: Gulf of Mexico | Statement: [Eastpoint, Franklin County, Florida, coastalCommunityOf, Gulf of Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalCommunityOf Context triple: [Eastpoint, Franklin County, Florida, coastalCommunityOf, Gulf of Mexico]
-
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.
coastalPeople
Indicates that the people are located in, originate from, or are closely associated with a coastal (seaside) area.
-
C.
coastalHub
Indicates a location functions as a primary center of activity, transport, or services situated on or very near a coastline.
-
D.
coastalCluster
Indicates a grouping of entities that are located near or along the same coastal area or shoreline.
-
E.
areCoastal
Indicates that the entities are located on or adjacent to a coastline or seashore.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f622323540819085ba63fa3ab9199d |
completed | May 2, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 7:11 a.m.