Triple
T20143709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ID |
E491241
|
entity |
| Predicate | alpha3Equivalent |
P43262
|
FINISHED |
| Object | IDN |
—
|
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: IDN | Statement: [ID, alpha3Equivalent, IDN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alpha3Equivalent Context triple: [ID, alpha3Equivalent, IDN]
-
A.
hasISO4217ThreeLetterCode
Indicates that an entity is associated with a specific three-letter currency code defined by the ISO 4217 standard.
-
B.
ISOCode
Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
-
C.
ISO3166-1Code
Indicates the standardized two- or three-letter country or territory code assigned under the ISO 3166-1 international standard.
-
D.
ISO639-1Equivalent
Indicates that two language identifiers are equivalent according to the ISO 639-1 two-letter language code standard.
-
E.
hasISO3166Alpha3Code
chosen
Indicates that an entity is associated with a specific three-letter country code defined by the ISO 3166-1 alpha-3 standard.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679cbc388190bb2b444a69a597a6 |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:33 p.m.