Triple
T35907637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSCE Summit |
E1038514
|
entity |
| Predicate | convenedWhen |
P186502
|
FINISHED |
| Object | major strategic decisions are needed |
—
|
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: major strategic decisions are needed | Statement: [OSCE Summit, convenedWhen, major strategic decisions are needed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convenedWhen Context triple: [OSCE Summit, convenedWhen, major strategic decisions are needed]
-
A.
convenedOn
Indicates that an event, meeting, or formal gathering took place or was held on a specific date or time.
-
B.
convenedAfter
Indicates that one event, meeting, or gathering was formally brought together at a time later than another specified event.
-
C.
convenedFor
Indicates that an event, meeting, or gathering was brought together for a specific purpose, topic, or beneficiary.
-
D.
convenedIn
Indicates that an event, meeting, or formal gathering was brought together and held at a specific location.
-
E.
convenesOn
Indicates that an event, group, or body holds a meeting or session at a specific time or date.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:07 p.m.