Triple
T2503341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mennonite World Conference |
E52518
|
entity |
| Predicate | organizesEventType |
P34559
|
FINISHED |
| Object | global assembly |
—
|
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: global assembly | Statement: [Mennonite World Conference, organizesEventType, global assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizesEventType Context triple: [Mennonite World Conference, organizesEventType, global assembly]
-
A.
eventTypeOrganized
chosen
Indicates that an entity organized or arranged a specific type or category of event.
-
B.
organisedEvent
Indicates that an entity planned, coordinated, and carried out an event.
-
C.
oftenOrganizedBy
Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or entity.
-
D.
organizes
Indicates that one entity arranges, coordinates, or structures activities, items, or people into an ordered or planned form for a particular purpose.
-
E.
alsoHostedEventType
Indicates that the same host was responsible for organizing or holding another event of a specified type.
- 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1cb4f6481908d4e0a1dc0d84d3c |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0bba5348190bb4637d3165cb339 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.