Triple
T7647159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treasure Coast |
E173153
|
entity |
| Predicate | sometimesIncludesCounty |
P29773
|
FINISHED |
| Object | Okeechobee 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: Okeechobee County | Statement: [Treasure Coast, sometimesIncludesCounty, Okeechobee County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesIncludesCounty Context triple: [Treasure Coast, sometimesIncludesCounty, Okeechobee County]
-
A.
includesCounty
Indicates that a larger geographic or administrative region contains or encompasses a specific county within its boundaries.
-
B.
sometimesIncludesTerritory
chosen
Indicates that one entity occasionally, but not consistently, encompasses or contains the territory of another entity.
-
C.
hasAdditionalCounty
Indicates that an entity is associated with one or more counties beyond its primary or originally specified county.
-
D.
inCounty
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
-
E.
traditionalCountyIncludes
Indicates that a traditional or historic county geographically contains or encompasses another area or entity within its boundaries.
- 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_69c6995360188190968ee57b72a1627f |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faf6328c8190bce0a3f8a17ef890 |
completed | March 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e9ef1c81909c8bff716541ac1f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:58 p.m.