Triple
T29383134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OHR |
E745184
|
entity |
| Predicate | meetingWherePowersDefined |
P12554
|
FINISHED |
| Object | 1997 Bonn Peace Implementation Council conference |
—
|
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: 1997 Bonn Peace Implementation Council conference | Statement: [OHR, meetingWherePowersDefined, 1997 Bonn Peace Implementation Council conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetingWherePowersDefined Context triple: [OHR, meetingWherePowersDefined, 1997 Bonn Peace Implementation Council conference]
-
A.
meetingPeriod
Indicates the time span or duration during which a meeting takes place.
-
B.
isPowerConference
Indicates that an athletic conference is considered a major or elite "power" conference within its sport or league.
-
C.
convenesUnder
chosen
Indicates that an entity holds or conducts a meeting, session, or gathering under the authority, auspices, or framework of another entity or arrangement.
-
D.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
-
E.
meetingLevel
Indicates the degree or intensity of interaction or engagement between participants in a meeting or meeting-like context.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669d007d08190bf0df2edbdb3e171 |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:36 p.m.