Triple
T7572046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Road 60 |
E179266
|
entity |
| Predicate | easternTerminusCounty |
P3569
|
FINISHED |
| Object | Indian River County |
—
|
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: Indian River County | Statement: [State Road 60, easternTerminusCounty, Indian River County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: easternTerminusCounty Context triple: [State Road 60, easternTerminusCounty, Indian River County]
-
A.
isEasternmostCountyOf
Indicates that a county is the geographically farthest east within the boundaries of a specified larger region or jurisdiction.
-
B.
easternTerminusState
Indicates the state in which the eastern terminus (end point) of something, such as a route or line, is located.
-
C.
startCounty
Indicates the county in which something (such as an event, route, or process) begins or originates.
-
D.
isCornerCountyOf
Indicates that a county lies at or near the corner where two or more larger administrative regions (such as states or districts) meet.
-
E.
terminusEast
chosen
Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f921b458819092e565a4d099bbaf |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.