Triple
T35929764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PL |
E1039125
|
entity |
| Predicate | usedAsUNDPCode |
P79582
|
FINISHED |
| Object | POL |
—
|
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: POL | Statement: [PL, usedAsUNDPCode, POL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsUNDPCode Context triple: [PL, usedAsUNDPCode, POL]
-
A.
correspondingUNCode
Indicates that there is a specific United Nations code that corresponds to or represents the given entity.
-
B.
usedInUNStatistics
Indicates that something is employed or referenced within official United Nations statistical data, classifications, or reporting.
-
C.
hasUNCode
chosen
Indicates that an entity is associated with a specific United Nations–assigned code that identifies it in UN systems or classifications.
-
D.
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.
-
E.
usesCodeName
Indicates that one entity refers to another entity by a code name or alias instead of its real or full designation.
- 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 3, 2026, 4:07 p.m.