Triple
T34446498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN General Assembly resolution 34/151 |
E884241
|
entity |
| Predicate | designatedCalendarYear |
P7173
|
FINISHED |
| Object | 1985 |
—
|
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: 1985 | Statement: [UN General Assembly resolution 34/151, designatedCalendarYear, 1985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatedCalendarYear Context triple: [UN General Assembly resolution 34/151, designatedCalendarYear, 1985]
-
A.
specifiedYear
Indicates that a particular year has been explicitly designated or identified in relation to the subject.
-
B.
appointmentYear
Indicates the year in which an entity was formally appointed to a role, position, or office.
-
C.
yearType
chosen
Indicates the classification or category assigned to a specific year (e.g., academic, fiscal, calendar, leap).
-
D.
planningYear
Indicates the year in which planning or preparation activities for something are scheduled or designated to occur.
-
E.
declaredYear
Indicates the year in which something was formally announced, established, or proclaimed.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: May 1, 2026, 2 a.m.