Triple
T27763755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jenaz |
E701544
|
entity |
| Predicate | usesISO3166-2Code |
P164530
|
FINISHED |
| Object | CH-GR |
—
|
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-GR | Statement: [Jenaz, usesISO3166-2Code, CH-GR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesISO3166-2Code Context triple: [Jenaz, usesISO3166-2Code, CH-GR]
-
A.
hasISO3166-2CodePrefix
Indicates that one entity’s ISO 3166-2 code begins with, or is prefixed by, the code of another entity.
-
B.
parentISO3166Code
Indicates that one geographic or political entity is hierarchically contained within or derived from another, as represented by its parent ISO 3166 country or region code.
-
C.
hasISO3166-1NumericCode
Indicates that an entity is associated with a specific ISO 3166-1 numeric country code.
-
D.
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.
-
E.
ISO3166-2DifferentFrom
Indicates that two ISO 3166-2 subdivision codes are explicitly distinct and should not be considered equivalent or interchangeable.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 4:29 p.m.