Triple
T9642537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida State Road 22 |
E233108
|
entity |
| Predicate | westernTerminusCounty |
P13603
|
FINISHED |
| Object | Bay County, Florida |
E40029
|
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: Bay County, Florida | Statement: [Florida State Road 22, westernTerminusCounty, Bay County, Florida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: westernTerminusCounty Context triple: [Florida State Road 22, westernTerminusCounty, Bay County, Florida]
-
A.
westernTerminusNear
Indicates that the western endpoint of one entity is located close to another entity.
-
B.
westernTerminusDetail
chosen
Indicates the specific endpoint location or characteristics associated with the western terminus of a route or linear feature.
-
C.
westernTerminusState
Indicates the state in which something (such as a route, line, or path) has its western endpoint or terminus.
-
D.
isEasternmostCountyOf
Indicates that a county is the geographically farthest east within the boundaries of a specified larger region or jurisdiction.
-
E.
isCornerCountyOf
Indicates that a county lies at or near the corner where two or more larger administrative regions (such as states or districts) meet.
- 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b7cda388190a38f96d78085f404 |
completed | April 1, 2026, 10:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a7a703cc5688190b03eb4c9699f6885 |
completed | Aug. 11, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:12 p.m.