Triple
T151487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN General Assembly Resolution 68/262 |
E3439
|
entity |
| Predicate | absent |
P4300
|
FINISHED |
| Object | 24 |
—
|
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: 24 | Statement: [UN General Assembly Resolution 68/262, absent, 24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: absent Context triple: [UN General Assembly Resolution 68/262, absent, 24]
-
A.
attendance
Indicates the relationship between an event and the people who are present at or participate in that event.
-
B.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
-
C.
assumes
Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
-
D.
doesNot
chosen
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
E.
appointedFor
Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580f55a88190b37b54ee0ed5ac7c |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565adaf48190b68ae4444ff83ccd |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.