Triple
T15013581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coskata Pond |
E377899
|
entity |
| Predicate | hasLandformNearby |
P940
|
FINISHED |
| Object | barrier beach system of Coskata and Coatue |
—
|
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: barrier beach system of Coskata and Coatue | Statement: [Coskata Pond, hasLandformNearby, barrier beach system of Coskata and Coatue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandformNearby Context triple: [Coskata Pond, hasLandformNearby, barrier beach system of Coskata and Coatue]
-
A.
hasHighestPointNear
Indicates that one entity’s highest point is located close to another specified entity or location.
-
B.
hasLandform
chosen
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
C.
nearestLandmass
Indicates that one landmass is the closest geographically to another specified point or landmass.
-
D.
nearbyMountainRegion
Indicates that one location is situated close to or within the surrounding area of a mountainous region.
-
E.
hasNearestMountain
Indicates that one entity is the closest mountain geographically relative to 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7613cec8190ac25e3f68c5d0edf |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:55 a.m.