Triple
T29797075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida State Road 710 |
E756582
|
entity |
| Predicate | runsInlandBetween |
P167885
|
FINISHED |
| Object | Treasure Coast |
—
|
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: Treasure Coast | Statement: [Florida State Road 710, runsInlandBetween, Treasure Coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsInlandBetween Context triple: [Florida State Road 710, runsInlandBetween, Treasure Coast]
-
A.
locatedInland
Indicates that something is situated away from the coast or shoreline, within the interior of a land area.
-
B.
connectsInlandRoutesTo
Indicates that one entity serves as a link or junction that enables inland transportation routes to reach or connect with another entity.
-
C.
connectsInlandToBorder
Indicates that an inland location is linked or provides a route to a border location.
-
D.
locatedBetweenRiver
Indicates that an entity is situated in the area or region between two segments or banks of a river, or between two rivers.
-
E.
betweenRiver
Indicates a spatial relationship where something is located in the area separating two rivers or lies in the intermediate region defined by them.
- F. None of above. chosen
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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f674e7548c81909acffee32ca126f9 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 29, 2026, 5:16 p.m.