Triple
T31058066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterprise, Florida |
E791448
|
entity |
| Predicate | locatedAcrossLakeFrom |
P203239
|
FINISHED |
| Object | Sanford, Florida |
—
|
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: Sanford, Florida | Statement: [Enterprise, Florida, locatedAcrossLakeFrom, Sanford, Florida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAcrossLakeFrom Context triple: [Enterprise, Florida, locatedAcrossLakeFrom, Sanford, Florida]
-
A.
locatedOnGreatLake
Indicates that something is situated on the shore or directly adjacent to one of the Great Lakes.
-
B.
locatedBetweenLakes
Indicates that something is situated in the area separating two lakes, with each lake on a different side of it.
-
C.
cityOnLake
Indicates that a city is located on the shore or edge of a particular lake.
-
D.
hasNearbyLake
Indicates that one entity is located close to or in the vicinity of a lake.
-
E.
locatedAcrossRiverFrom
Indicates that one entity is situated on the opposite side of a river relative to another entity.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01416f8a8c8190abc12f68bd23dcc3 |
completed | May 11, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_6a013f3bc2e48190a51ec2707bbdd474 |
completed | May 11, 2026, 2:30 a.m. |
| PDg | Predicate description generation | batch_6a01416eb9588190ad74541d0640a4ba |
completed | May 11, 2026, 2:39 a.m. |
Created at: April 29, 2026, 9 p.m.