Triple
T25598821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 3166-2:IT |
E641729
|
entity |
| Predicate | subdivisionTypeIncluded |
P109605
|
FINISHED |
| Object | region |
—
|
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: region | Statement: [ISO 3166-2:IT, subdivisionTypeIncluded, region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subdivisionTypeIncluded Context triple: [ISO 3166-2:IT, subdivisionTypeIncluded, region]
-
A.
hasTypeOfSubdivision
Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
-
B.
subdivisionType0
chosen
Indicates that the referenced entity is classified as the primary (level 0) type of administrative or territorial subdivision within a larger jurisdiction.
-
C.
subdivisionStatus
Indicates the current state or phase of a subdivision process or classification for an entity.
-
D.
subdividedBy
Indicates that something is divided into smaller parts or sections by another entity or criterion.
-
E.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 4:30 p.m.