Triple
T18941964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 3166-2:SM |
E463403
|
entity |
| Predicate | usesNumericSubdivisionCode |
P133889
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ISO 3166-2:SM, usesNumericSubdivisionCode, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNumericSubdivisionCode Context triple: [ISO 3166-2:SM, usesNumericSubdivisionCode, yes]
-
A.
hasSubdivisionCode
Indicates that an entity is associated with a specific code identifying one of its internal subdivisions (such as a state, province, or region).
-
B.
hasNationalSubdivisionType
Indicates that an entity is associated with a specific type or category of national-level administrative subdivision (e.g., state, province, region).
-
C.
hasSubdivisionCodePart
Indicates that an entity’s subdivision code includes or is composed of the referenced code segment or component.
-
D.
hasSubdivisionStandard
Indicates that a governing standard or specification defines how an entity is to be subdivided into smaller parts or units.
-
E.
isSubdivisionUsedFor
Indicates that a particular subdivision (such as a region, section, or part of something) is utilized for a specified purpose or function.
- F. None of above. chosen
Provenance (4 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3ec857081908da0f974604f2c65 |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 11:59 a.m.