Triple
T336891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMO Assembly |
E6747
|
entity |
| Predicate | convenesEvery |
P1309
|
FINISHED |
| Object | two years |
—
|
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: two years | Statement: [IMO Assembly, convenesEvery, two years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convenesEvery Context triple: [IMO Assembly, convenesEvery, two years]
-
A.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
-
B.
convenesBefore
Indicates that one event or gathering is convened and completed before another specified event or gathering begins.
-
C.
convenes
Indicates bringing people or groups together to formally meet, discuss, or deliberate on a particular matter.
-
D.
meetsEvery
Indicates that one entity encounters or comes into contact with every member of a specified set of entities.
-
E.
convenesRegularSession
chosen
Indicates that an entity formally brings together a group or body for its routine or scheduled meeting.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eac950388190829875a07d821ddf |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94f049881908f10bb6548a8bb2e |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.