Triple
T31127910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROU |
E793409
|
entity |
| Predicate | codeForCountryWithISO2 |
P49426
|
FINISHED |
| Object | RO |
—
|
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: RO | Statement: [ROU, codeForCountryWithISO2, RO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeForCountryWithISO2 Context triple: [ROU, codeForCountryWithISO2, RO]
-
A.
ISOCode
Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
-
B.
iso3166CodeBasedOn
chosen
Indicates that one code or designation is derived from, corresponds to, or is assigned on the basis of a specific ISO 3166 country or region code.
-
C.
continentCode
Indicates the standardized code assigned to the continent with which an entity is associated.
-
D.
ISOCodeContext
Indicates the contextual framework or domain within which a particular ISO code is defined, interpreted, or applied.
-
E.
hasISOCode
Indicates that an entity is associated with a specific standardized ISO code that uniquely identifies it according to ISO conventions.
- 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:05 p.m.