Triple
T2568471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CHOGM communiqué |
E57607
|
entity |
| Predicate | approvedAt |
P40249
|
FINISHED |
| Object | plenary session of CHOGM |
—
|
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: plenary session of CHOGM | Statement: [CHOGM communiqué, approvedAt, plenary session of CHOGM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approvedAt Context triple: [CHOGM communiqué, approvedAt, plenary session of CHOGM]
-
A.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
B.
approvedInCountry
Indicates that an entity has received official authorization or approval within the jurisdiction of a specified country.
-
C.
approvalDate
Indicates the date on which an action, request, or item was formally approved.
-
D.
approvalProcess
Indicates the sequence of steps, decisions, and authorizations required for something to be formally reviewed and approved.
-
E.
approves
Indicates that one entity formally accepts, authorizes, or agrees to a proposal, action, or decision made by another entity.
- 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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd36191848190b6255fa9029429bd |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0cc8d308190ae7aa32b8f5ae2e5 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1aa13a08190a8757c017d8a2478 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:48 p.m.