Triple
T27422853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Census Bureau Moore County region |
E693092
|
entity |
| Predicate | countyCensusCode |
P10086
|
FINISHED |
| Object | 125 |
—
|
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: 125 | Statement: [United States Census Bureau Moore County region, countyCensusCode, 125]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countyCensusCode Context triple: [United States Census Bureau Moore County region, countyCensusCode, 125]
-
A.
hasCountyCode
chosen
Indicates that an entity is associated with a specific county identified by a standardized county code.
-
B.
censusNumber
Indicates the unique identifier or count assigned to an entity within an official census record.
-
C.
hasCountyCodeType
Indicates that an entity is associated with a specific type or classification of county code.
-
D.
censusRegion
Indicates the broader census-defined geographic region in which an entity (such as a place or population unit) is located or classified.
-
E.
districtCode
Indicates that an entity is associated with, or identified by, a specific administrative district code.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: April 27, 2026, 12:36 p.m.