Triple
T34581791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USUNESCO |
E887925
|
entity |
| Predicate | representsPolicyPositionsAt |
P33187
|
FINISHED |
| Object | UNESCO |
—
|
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: UNESCO | Statement: [USUNESCO, representsPolicyPositionsAt, UNESCO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsPolicyPositionsAt Context triple: [USUNESCO, representsPolicyPositionsAt, UNESCO]
-
A.
representsPositionOn
Indicates that one entity specifies or defines the spatial or logical position of another entity within a given context.
-
B.
policyRepresentation
chosen
Indicates that one entity serves as a formal expression, model, or encoding of a policy defined or governed by another entity.
-
C.
positionRepresented
Indicates that one entity serves as a representation or proxy for a particular position, role, or office held by another entity.
-
D.
politicalPositionAssociated
Indicates that there is an association between an entity and a specific political position, role, or office.
-
E.
policyStance
Indicates the position or viewpoint an entity holds regarding a specific policy or set of policies.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: May 1, 2026, 2:03 a.m.