Triple
T25598837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 3166-2:IT |
E641729
|
entity |
| Predicate | governsCodeUniquenessWithin |
P75156
|
FINISHED |
| Object | Italian territory |
—
|
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: Italian territory | Statement: [ISO 3166-2:IT, governsCodeUniquenessWithin, Italian territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsCodeUniquenessWithin Context triple: [ISO 3166-2:IT, governsCodeUniquenessWithin, Italian territory]
-
A.
isUniqueWithinStandard
Indicates that an entity is the only one of its kind within the scope or constraints of a given standard or specification.
-
B.
isUniqueWithinCountry
Indicates that an entity is the only one of its kind within the boundaries of a specific country.
-
C.
isUniqueWithinSystem
Indicates that an entity exists only once and has no duplicates within the defined system or scope.
-
D.
isUniqueWithinISO3166-1Alpha2
chosen
Indicates that the referenced entity is unique within the scope defined by a specific ISO 3166-1 alpha-2 country code.
-
E.
typeOfUniqueness
Indicates that one entity’s uniqueness is characterized, classified, or constrained by the specific kind or mode of uniqueness associated with another 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 21, 2026, 4:30 p.m.