Triple
T1044514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 3166-3 |
E22545
|
entity |
| Predicate | usesAsBasis |
P7051
|
FINISHED |
| Object | former ISO 3166-1 alpha-2 codes |
—
|
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: former ISO 3166-1 alpha-2 codes | Statement: [ISO 3166-3, usesAsBasis, former ISO 3166-1 alpha-2 codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAsBasis Context triple: [ISO 3166-3, usesAsBasis, former ISO 3166-1 alpha-2 codes]
-
A.
usedAsBasisFor
chosen
Indicates that one entity serves as the foundation, reference, or starting point upon which another entity is developed, derived, justified, or constructed.
-
B.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
C.
isBasedOn
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
-
D.
areBasedOn
Indicates that one entity is founded, derived, or developed from the principles, content, or structure of another entity.
-
E.
isUsedUnder
Indicates that one entity is utilized or applied within the context, conditions, or framework defined by another entity.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b84937688190a5899af2104002df |
completed | March 1, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69a4b72ba60881908b017ef3b2b9645e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.