Triple
T34092123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Region (Census Region 3) |
E874323
|
entity |
| Predicate | censusRegionCode |
P5151
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [South Region (Census Region 3), censusRegionCode, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: censusRegionCode Context triple: [South Region (Census Region 3), censusRegionCode, 3]
-
A.
censusRegion
chosen
Indicates the broader census-defined geographic region in which an entity (such as a place or population unit) is located or classified.
-
B.
hasCensusDivisionCode
Indicates that an entity is associated with a specific census division identified by a particular code.
-
C.
subregionCodeFor
Indicates that one entity is the code assigned to identify a specific subregion of the other entity.
-
D.
countyRegion
Indicates that a county is located within, or is administratively part of, a larger geographic region.
-
E.
hasCongressionalDistrictCode
Indicates that an entity is associated with a specific congressional district identified by a particular 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70c16095081908ffa34ea55556a65 |
completed | May 3, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:52 a.m.