Triple
T29918814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Methodist annual conferences |
E759864
|
entity |
| Predicate | convene |
P982
|
FINISHED |
| Object | clergy members |
—
|
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: clergy members | Statement: [United Methodist annual conferences, convene, clergy members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convene Context triple: [United Methodist annual conferences, convene, clergy members]
-
A.
convenes
chosen
Indicates bringing people or groups together to formally meet, discuss, or deliberate on a particular matter.
-
B.
convenesAs
Indicates that an entity brings together or assembles a group, body, or session in a particular role or capacity.
-
C.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
-
D.
convenesUnder
Indicates that an entity holds or conducts a meeting, session, or gathering under the authority, auspices, or framework of another entity or arrangement.
-
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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 29, 2026, 6:13 p.m.