Triple
T5261577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 6166 |
E118835
|
entity |
| Predicate | countryCodeFormat |
P62608
|
FINISHED |
| Object | Two-letter ISO 3166-1 alpha-2 code |
—
|
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: Two-letter ISO 3166-1 alpha-2 code | Statement: [ISO 6166, countryCodeFormat, Two-letter ISO 3166-1 alpha-2 code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryCodeFormat Context triple: [ISO 6166, countryCodeFormat, Two-letter ISO 3166-1 alpha-2 code]
-
A.
countryCodePart
Indicates that one entity is a segment or component of a standardized country code associated with another entity.
-
B.
UICCountryCode
Indicates that an entity is associated with a specific country identified by its UIC (International Union of Railways) country code.
-
C.
callingCodeType
Indicates the type or category of a telephone calling code associated with an entity.
-
D.
callingCode
Indicates the telephone country or area code associated with an entity for making phone calls.
-
E.
countryCodeManaged
Indicates that an entity is responsible for administering or controlling the specified country code.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bd0c5f48190a1be89314c59f96b |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7bcabe58819096255672664513b1 |
completed | March 20, 2026, 4:54 p.m. |
Created at: March 20, 2026, 1:50 p.m.