Triple
T2659426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ponce de Leon, Florida |
E54690
|
entity |
| Predicate | waterBodyTypeNearby |
P1011
|
FINISHED |
| Object | freshwater springs |
—
|
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: freshwater springs | Statement: [Ponce de Leon, Florida, waterBodyTypeNearby, freshwater springs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterBodyTypeNearby Context triple: [Ponce de Leon, Florida, waterBodyTypeNearby, freshwater springs]
-
A.
nearbyWatercourse
Indicates that one entity is located close to or alongside a natural or artificial watercourse, such as a river, stream, or canal.
-
B.
connectedBodyOfWater
Indicates that two geographic locations are linked by a continuous body of water through which water can flow between them.
-
C.
bodyOfWater
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
D.
waterbodyType
chosen
Indicates the classification of a water body according to its type (e.g., river, lake, ocean, etc.).
-
E.
nearbyWaterfall
Indicates that the entity is located close to or within a short distance of a waterfall.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd94f3b1881909bd36cfe61c254a5 |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.