Triple
T35380232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 9362 |
E1022622
|
entity |
| Predicate | countryCodeStandardUsed |
P62608
|
FINISHED |
| Object | ISO 3166-1 alpha-2 |
E3184
|
NE 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: ISO 3166-1 alpha-2 | Statement: [ISO 9362, countryCodeStandardUsed, ISO 3166-1 alpha-2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryCodeStandardUsed Context triple: [ISO 9362, countryCodeStandardUsed, ISO 3166-1 alpha-2]
-
A.
numericCountryCode
Indicates that a country is associated with a specific numeric code that uniquely identifies it.
-
B.
countryCodeMeaning
Indicates the semantic meaning or description associated with a given country code.
-
C.
countryCodeFormat
chosen
Indicates the standardized structure or pattern in which a country's code must be represented.
-
D.
continentCode
Indicates the standardized code assigned to the continent with which an entity is associated.
-
E.
telephoneSystemCountry
Indicates that a telephone system operates within, or is associated with, a specific country.
- F. None of above.
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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a01bcd39760819081807a02eb1939d1 |
completed | May 11, 2026, 11:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a382cbcb1388190b89aa1e2e389ef36 |
completed | June 21, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_6a01bc3f1c74819087580e3134affc60 |
completed | May 11, 2026, 11:23 a.m. |
Created at: May 3, 2026, 4:03 p.m.