Triple
T24029350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moniteau County, Missouri |
E595052
|
entity |
| Predicate | inU.S.Census |
P53422
|
FINISHED |
| Object | United States Census |
—
|
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: United States Census | Statement: [Moniteau County, Missouri, inU.S.Census, United States Census]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inU.S.Census Context triple: [Moniteau County, Missouri, inU.S.Census, United States Census]
-
A.
census
Indicates that an official count or survey is conducted to determine the number and characteristics of a population within a defined area or group.
-
B.
censusNumber
Indicates the unique identifier or count assigned to an entity within an official census record.
-
C.
censusReportedIn
chosen
Indicates that information about a population or demographic count is documented or recorded in a specific census.
-
D.
rankInUS2010Census
Indicates the numerical position of an entity in the ranking of occurrences within the 2010 United States Census.
-
E.
frequencyOfCensus
Indicates how often a census is conducted or occurs within a given context or jurisdiction.
- 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_69e288bf45f08190a1b6ed8cd0b9e86b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d76e10fc8190afa60c618a4398ee |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:54 p.m.