Triple
T13839924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Plenary Meeting |
E332629
|
entity |
| Predicate | discussionFormat |
P105218
|
FINISHED |
| Object | plenary sessions |
—
|
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 sessions | Statement: [World Plenary Meeting, discussionFormat, plenary sessions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discussionFormat Context triple: [World Plenary Meeting, discussionFormat, plenary sessions]
-
A.
discussionStyle
Indicates the manner or approach with which one party conducts or participates in a discussion with another.
-
B.
dialogueFormat
chosen
Indicates the specific structure or style in which a dialogue or conversational exchange is presented or encoded between entities.
-
C.
discussionPublic
Indicates that a discussion is accessible to the general public rather than being restricted or private.
-
D.
forum
Indicates that an entity hosts or is associated with an online discussion space where users can post messages and interact.
-
E.
dialogueForm
Indicates that one entity takes the form or structure of a dialogue, typically involving conversational or interactive exchange between parties.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02ae5e4c8190ad85ad2968bc71b2 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.