Triple
T26965754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rial |
E679167
|
entity |
| Predicate | hasISOCodeVariant |
P163078
|
FINISHED |
| Object | IRR |
—
|
NE NERFINISHED |
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: IRR | Statement: [rial, hasISOCodeVariant, IRR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISOCodeVariant Context triple: [rial, hasISOCodeVariant, IRR]
-
A.
hasISOCode
Indicates that an entity is associated with a specific standardized ISO code that uniquely identifies it according to ISO conventions.
-
B.
hasISOCodeType
Indicates that an entity is associated with a specific type or category of ISO code (e.g., country code, currency code, language code).
-
C.
hasISOCodeLevel
Indicates that an entity is associated with a specific level or tier within an ISO (International Organization for Standardization) coding system.
-
D.
haveISO639Code
Indicates that a language or linguistic entity is associated with a specific ISO 639 standardized language code.
-
E.
hasISO15924Number
Indicates that an entity (a writing script) is associated with a specific numeric code defined by the ISO 15924 standard.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 6:35 a.m.