Triple
T38544653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DZ |
E924932
|
entity |
| Predicate | correspondingUNDPCode |
P79582
|
FINISHED |
| Object | DZA |
—
|
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: DZA | Statement: [DZ, correspondingUNDPCode, DZA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondingUNDPCode Context triple: [DZ, correspondingUNDPCode, DZA]
-
A.
recognizedByUNAsPartOf
Indicates that an entity is officially acknowledged or accepted by the United Nations as belonging to, or constituting a component of, another specified entity or grouping.
-
B.
hasUNCode
chosen
Indicates that an entity is associated with a specific United Nations–assigned code that identifies it in UN systems or classifications.
-
C.
UNRegion
Indicates that an entity belongs to, or is associated with, a specific United Nations–defined geographic region.
-
D.
isMainUNPlatformFor
Indicates that one entity serves as the primary United Nations platform or forum for activities, discussions, or coordination related to another entity.
-
E.
UNMemberStateCode
Indicates that an entity is assigned a specific standardized code denoting its status as a member state of the United Nations.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:32 p.m.