Triple
T35279287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Region |
E1018890
|
entity |
| Predicate | censusDivisionCode_SouthAtlantic |
P132200
|
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, censusDivisionCode_SouthAtlantic, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: censusDivisionCode_SouthAtlantic Context triple: [South Region, censusDivisionCode_SouthAtlantic, 3]
-
A.
hasCensusDivisionCode
chosen
Indicates that an entity is associated with a specific census division identified by a particular code.
-
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.
stateSubdivisionCode
Indicates the standardized code that identifies a specific subdivision (such as a state, province, or region) within a larger country or territory.
-
D.
USStateRegion
Indicates that a U.S. state is located within or belongs to a particular geographic region of the United States.
-
E.
USStateSubdivision
Indicates that one entity is an administrative subdivision (such as a county, parish, or borough) within a U.S. state represented by the other entity.
- 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_69f76de5c4788190896ad598ae7d6bc6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fd7c9148190848a6671583dc146 |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.