Triple
T3831400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esperanto movement |
E91018
|
entity |
| Predicate | hadUNESCOResolutionsIn |
P30960
|
FINISHED |
| Object | 1954 |
—
|
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: 1954 | Statement: [Esperanto movement, hadUNESCOResolutionsIn, 1954]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadUNESCOResolutionsIn Context triple: [Esperanto movement, hadUNESCOResolutionsIn, 1954]
-
A.
UNResolution
Indicates that there exists a formal decision or declaration adopted by the United Nations, typically expressing a collective position, directive, or recommendation regarding an issue.
-
B.
UNResolutionDate
Indicates the calendar date on which a specific United Nations resolution was formally adopted or passed.
-
C.
UNResolutionNumber
Indicates the specific numerical identifier assigned to a United Nations resolution that references or governs the related entities or actions.
-
D.
UNResolutionYear
chosen
Indicates the calendar year in which a specific United Nations resolution was formally adopted or issued.
-
E.
hasPeacekeepingForcesFrom
Indicates that an entity hosts or is supported by peacekeeping forces that originate from another specified entity.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb86207c81908f40a01fe27f6a0b |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.