Triple
T3029766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midway, Florida |
E82863
|
entity |
| Predicate | isInLandlockedCounty |
P45084
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Midway, Florida, isInLandlockedCounty, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInLandlockedCounty Context triple: [Midway, Florida, isInLandlockedCounty, true]
-
A.
isInlandTown
Indicates that a town is located away from the coast, without direct access to the sea or ocean.
-
B.
isInCountySubdivision
Indicates that one entity (typically a place or address) is located within the boundaries of a specific county subdivision.
-
C.
isRuralCounty
Indicates that a given county is classified as rural rather than urban based on demographic, geographic, or administrative criteria.
-
D.
isInCountySeatOf
Indicates that one entity is located within the town or city that serves as the administrative center (county seat) of a specified county.
-
E.
isInUSState
Indicates that one entity (typically a place or location) is geographically located within the boundaries of a specific U.S. state.
- 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9aecd384819085d15f701add7c44 |
completed | March 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 3 p.m.