Triple
T660011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN Security Council Resolution 678 |
E11732
|
entity |
| Predicate | meetingNumber |
P18167
|
FINISHED |
| Object | 2963 |
—
|
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: 2963 | Statement: [UN Security Council Resolution 678, meetingNumber, 2963]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetingNumber Context triple: [UN Security Council Resolution 678, meetingNumber, 2963]
-
A.
meetingType
Indicates the specific category or format of a meeting that characterizes how it is organized or conducted.
-
B.
notableMeeting
Indicates that two or more entities participated together in a meeting considered significant or noteworthy in some context.
-
C.
meetingFrequency
Indicates how often a meeting or recurring gathering takes place over a given period.
-
D.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
-
E.
hasMeeting
Indicates that one entity is scheduled to participate in or hold a meeting with another entity or at a specific time or place.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0f55f7481909e052a25bd12d455 |
completed | March 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69a49d1406ec8190abf546549264c85d |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a4a0f405748190ba72a9cfe946a8ec |
completed | March 1, 2026, 8:26 p.m. |
Created at: March 1, 2026, 7:36 p.m.