Triple
T35853832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Census of Kentucky counties |
E1036441
|
entity |
| Predicate | coversAllCountiesIn |
P193278
|
FINISHED |
| Object | Kentucky |
—
|
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: Kentucky | Statement: [U.S. Census of Kentucky counties, coversAllCountiesIn, Kentucky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversAllCountiesIn Context triple: [U.S. Census of Kentucky counties, coversAllCountiesIn, Kentucky]
-
A.
eachCountyHas
Indicates that for every county in a given set or context, there exists at least one associated item, attribute, or entity satisfying a specified condition.
-
B.
includesCounty
Indicates that a larger geographic or administrative region contains or encompasses a specific county within its boundaries.
-
C.
hasNumberOfCounties
Indicates the relationship that specifies how many counties are associated with or contained within a given entity.
-
D.
includesMostOfState
Indicates that one geographic or political entity contains the majority of the area or extent of a given state within its boundaries.
-
E.
inCounty
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
| PDg | Predicate description generation | batch_69fd3d45ccb8819082f15e60bd33afc9 |
completed | May 8, 2026, 1:32 a.m. |
Created at: May 3, 2026, 4:06 p.m.