Triple
T10965482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford County |
E259083
|
entity |
| Predicate | censusDivisionCode |
P30519
|
FINISHED |
| Object | 3532 |
—
|
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: 3532 | Statement: [Oxford County, censusDivisionCode, 3532]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: censusDivisionCode Context triple: [Oxford County, censusDivisionCode, 3532]
-
A.
censusDivisionType
Indicates the classification of a census division according to its official administrative or statistical type.
-
B.
censusRegion
Indicates the broader census-defined geographic region in which an entity (such as a place or population unit) is located or classified.
-
C.
censusSubdivisionType
Indicates the specific administrative or geographic category assigned to a census subdivision (e.g., city, town, rural area) within a census system.
-
D.
hasDivisionCode
chosen
Indicates that an entity is associated with a specific division identifier or code within an organizational or classification structure.
-
E.
governingSubdivision
Indicates that one administrative or political unit serves as the governing authority over a smaller, subordinate territorial subdivision.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77148c4588190ad0f2b54ee4bab98 |
completed | April 9, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_69d72e8c27cc81908050590b7a04cafd |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:24 p.m.