Triple
T8933207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Security Council Resolution 1509 |
E212706
|
entity |
| Predicate | adoptedAtMeetingNumber |
P86264
|
FINISHED |
| Object | 4820 |
—
|
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: 4820 | Statement: [United Nations Security Council Resolution 1509, adoptedAtMeetingNumber, 4820]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedAtMeetingNumber Context triple: [United Nations Security Council Resolution 1509, adoptedAtMeetingNumber, 4820]
-
A.
adoptedAtEvent
Indicates that an entity formally became an adopter or was officially adopted during a specific event.
-
B.
adoptedAt
Indicates the time or date at which an adoption event took place.
-
C.
adoptedAtSameConferenceAs
Indicates that two entities were adopted during the same conference event or session.
-
D.
convenedOn
Indicates that an event, meeting, or formal gathering took place or was held on a specific date or time.
-
E.
convenedFor
Indicates that an event, meeting, or gathering was brought together for a specific purpose, topic, or beneficiary.
- F. None of above. chosen
Provenance (4 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc668fa87c8190bfeda820368b89e4 |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc608331f88190bcb500ff63527f8a |
completed | April 1, 2026, 12:02 a.m. |
Created at: March 30, 2026, 6:57 p.m.