Triple
T27422849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Census Bureau Moore County region |
E693092
|
entity |
| Predicate | usesGeographicUnit |
P116678
|
FINISHED |
| Object | county-equivalent |
—
|
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: county-equivalent | Statement: [United States Census Bureau Moore County region, usesGeographicUnit, county-equivalent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGeographicUnit Context triple: [United States Census Bureau Moore County region, usesGeographicUnit, county-equivalent]
-
A.
hasGeographicType
chosen
Indicates that an entity is associated with or classified by a specific type or category of geographic feature or area.
-
B.
geographicContext
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
-
C.
geographicalUsage
Indicates that something is used, applied, or occurs within a particular geographic area or region.
-
D.
geographicDivision
Indicates that one place is an administrative or territorial subdivision of another place.
-
E.
containsGeographicalArea
Indicates that one geographical area spatially encompasses or includes another geographical area 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62d1e948c8190aadd4607ec8f91db |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:36 p.m.