Triple
T32538371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durma |
E831650
|
entity |
| Predicate | hasISO3166-1Alpha2Country |
P176786
|
FINISHED |
| Object | SA |
—
|
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: SA | Statement: [Durma, hasISO3166-1Alpha2Country, SA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISO3166-1Alpha2Country Context triple: [Durma, hasISO3166-1Alpha2Country, SA]
-
A.
usesISO3166-2Code
Indicates that an entity employs or references a subdivision identifier defined by the ISO 3166-2 standard.
-
B.
hasISO3166-1NumericCode
Indicates that an entity is associated with a specific ISO 3166-1 numeric country code.
-
C.
hasISO3166-2CodePrefix
Indicates that one entity’s ISO 3166-2 code begins with, or is prefixed by, the code of another entity.
-
D.
hasISO3166Alpha3Code
Indicates that an entity is associated with a specific three-letter country code defined by the ISO 3166-1 alpha-3 standard.
-
E.
isUniqueWithinISO3166-1Alpha2
Indicates that the referenced entity is unique within the scope defined by a specific ISO 3166-1 alpha-2 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6f37f36ac8190b1bff8711d6771cb |
completed | May 3, 2026, 7:04 a.m. |
Created at: May 1, 2026, 1:01 a.m.