Triple
T10105150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US-DC |
E216298
|
entity |
| Predicate | regionTypeInStandard |
P1828
|
FINISHED |
| Object | District |
—
|
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: District | Statement: [US-DC, regionTypeInStandard, District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionTypeInStandard Context triple: [US-DC, regionTypeInStandard, District]
-
A.
regionType
chosen
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
-
B.
regionStandard
Indicates that something conforms to, is defined by, or is governed according to the official standards or norms of a particular region.
-
C.
regionTypeEast
Indicates that one region is classified as being of a certain type specifically in the eastern part of a larger area or reference frame.
-
D.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification system.
-
E.
regionTypeWest
Indicates that one region is of a specified type and is located to the west of another region.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd09dde888190bb550a3cd0b204fe |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:03 p.m.