Triple
T27246488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastpoint, Florida |
E687358
|
entity |
| Predicate | nearestBarrierIsland |
P19486
|
FINISHED |
| Object | St. George Island |
E1646205
|
NE 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: St. George Island | Statement: [Eastpoint, Florida, nearestBarrierIsland, St. George Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestBarrierIsland Context triple: [Eastpoint, Florida, nearestBarrierIsland, St. George Island]
-
A.
closestIsland
Indicates that one island is the nearest island to another island, compared to all other islands in consideration.
-
B.
nearIsland
chosen
Indicates that one entity is located close to or in the vicinity of an island.
-
C.
nearestTownOutsideIsland
Indicates the relationship where a town is identified as the closest town that is not located on the specified island.
-
D.
nearbyAtoll
Indicates that one entity (typically a location or feature) is situated close to or in the vicinity of an atoll.
-
E.
neighboringIsland
Indicates that one island is geographically adjacent to or very close to another island, typically separated only by a narrow body of water.
- F. None of above.
Provenance (4 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38cb70ea788190a694e7363c777a3c |
completed | June 22, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 10:42 a.m.