Triple
T15077735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borden County |
E380048
|
entity |
| Predicate | hasNoIncorporatedCities |
P117226
|
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: [Borden County, hasNoIncorporatedCities, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoIncorporatedCities Context triple: [Borden County, hasNoIncorporatedCities, true]
-
A.
hasNoMunicipalGovernment
Indicates that the entity lacks its own municipal governing body or local city/town government.
-
B.
hasIndependentCity
Indicates that a larger administrative region or entity contains a city that is administratively independent from the surrounding local jurisdictions.
-
C.
hasCapitalCityWithin
Indicates that a specified capital city is geographically located within the boundaries of a given region or country.
-
D.
hasNumberOfComponentCities
Indicates the relationship that specifies how many component cities are contained within or associated with a given entity.
-
E.
hasInlandCity
Indicates that one entity has, contains, or is associated with a city located inland (away from the coast or major bodies of water).
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff7fe5a208190823900b25e298dab |
completed | April 15, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:03 a.m.