Triple
T18373489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ES |
E446246
|
entity |
| Predicate | hasAssociatedUNDPCode |
P79582
|
FINISHED |
| Object | ESP |
—
|
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: ESP | Statement: [ES, hasAssociatedUNDPCode, ESP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedUNDPCode Context triple: [ES, hasAssociatedUNDPCode, ESP]
-
A.
hasUNCode
chosen
Indicates that an entity is associated with a specific United Nations–assigned code that identifies it in UN systems or classifications.
-
B.
hasUNOrgan
Indicates that an entity is a member of, affiliated with, or otherwise formally associated with a specified United Nations body or organ.
-
C.
hasUNESCORelation
Indicates a formal relationship or association between an entity and UNESCO, such as recognition, designation, partnership, or program involvement.
-
D.
hasOrganizationalCode
Indicates that an entity is associated with a specific organizational code used to identify it within an organization’s structure or system.
-
E.
hasProvincialCode
Indicates that an entity is associated with a specific provincial code that identifies its province or administrative region.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e517561edc8190b5d2834707ab662b |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:45 a.m.