Triple
T15220294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 3166-2:GS |
E363747
|
entity |
| Predicate | subdivisionsDefined |
P50774
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [ISO 3166-2:GS, subdivisionsDefined, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subdivisionsDefined Context triple: [ISO 3166-2:GS, subdivisionsDefined, 0]
-
A.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
-
B.
subdividedBy
Indicates that something is divided into smaller parts or sections by another entity or criterion.
-
C.
hasSubdivisionStandard
chosen
Indicates that a governing standard or specification defines how an entity is to be subdivided into smaller parts or units.
-
D.
hasTypeOfSubdivision
Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
-
E.
hasSubdivisionCode
Indicates that an entity is associated with a specific code identifying one of its internal subdivisions (such as a state, province, or 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007709d3881908384f0fe1e0218d0 |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:11 a.m.