Triple
T16961875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | international expert working groups |
E411449
|
entity |
| Predicate | isConvenedBy |
P12500
|
FINISHED |
| Object | intergovernmental organization |
—
|
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: intergovernmental organization | Statement: [international expert working groups, isConvenedBy, intergovernmental organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConvenedBy Context triple: [international expert working groups, isConvenedBy, intergovernmental organization]
-
A.
canBeConvenedBy
chosen
Indicates that an entity (such as a group, body, or meeting) may be formally brought together or assembled by a specified agent or authority.
-
B.
convenedFor
Indicates that an event, meeting, or gathering was brought together for a specific purpose, topic, or beneficiary.
-
C.
conventionSigned
Indicates that an entity has formally agreed to and signed a specific convention or treaty.
-
D.
canConcurIn
Indicates that one entity is able or permitted to agree with, coincide with, or participate jointly in the same event, decision, or condition as another entity.
-
E.
convenedIn
Indicates that an event, meeting, or formal gathering was brought together and held at a specific location.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d021c5508190b6e3106554c07a9c |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9cddf88190bc42709604047353 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.