Triple
T26166931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baar |
E654279
|
entity |
| Predicate | belongsToISO3166-2 |
P164530
|
FINISHED |
| Object | CH-ZG |
—
|
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: CH-ZG | Statement: [Baar, belongsToISO3166-2, CH-ZG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToISO3166-2 Context triple: [Baar, belongsToISO3166-2, CH-ZG]
-
A.
hasISO3166-2CodePrefix
Indicates that one entity’s ISO 3166-2 code begins with, or is prefixed by, the code of another entity.
-
B.
usesISO3166-2Code
chosen
Indicates that an entity employs or references a subdivision identifier defined by the ISO 3166-2 standard.
-
C.
isInUnitedStatesMunicipalHierarchy
Indicates that one administrative or governmental unit occupies a specific level or position within the municipal hierarchy of the United States (e.g., city, town, county, or similar local jurisdiction).
-
D.
hasISO3166-1Alpha2Country
Indicates that an entity is associated with a country identified by its ISO 3166-1 alpha-2 two-letter country code.
-
E.
associatedSubdivisionISO3166-1Alpha2
Indicates that a subdivision (such as a state or province) is associated with a specific country identified by its ISO 3166-1 alpha-2 code.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 26, 2026, 8:33 p.m.