Triple
T3123646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Florida |
E65243
|
entity |
| Predicate | northernBoundaryExtendedTo |
P45502
|
FINISHED |
| Object | 32°28′ north latitude |
—
|
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: 32°28′ north latitude | Statement: [West Florida, northernBoundaryExtendedTo, 32°28′ north latitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: northernBoundaryExtendedTo Context triple: [West Florida, northernBoundaryExtendedTo, 32°28′ north latitude]
-
A.
northernBoundaryReference
Indicates the feature or element that serves as the reference for defining the northern boundary of something.
-
B.
southernBoundaryReference
Indicates that one entity is used as the reference or defining limit for the southern boundary of another entity.
-
C.
westernBoundaryReference
Indicates the reference feature or limit that defines the western boundary of an entity or area.
-
D.
formsNorthernExtentOf
Indicates that one entity constitutes or defines the northernmost boundary or limit of another entity.
-
E.
fareBoundaryBetween
Indicates that there is a dividing line or zone where one fare region, zone, or pricing scheme ends and another begins.
- 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_69ad8580c72481909672d37acf647893 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada52c105c8190b8128e66d9b9e8a0 |
completed | March 8, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f7c21c819087e9992f5fe30a37 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:04 p.m.