Triple
T17070913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Tulle |
E414214
|
entity |
| Predicate | mayConvocate |
P87355
|
FINISHED |
| Object | diocesan synod in Tulle |
—
|
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: diocesan synod in Tulle | Statement: [Bishop of Tulle, mayConvocate, diocesan synod in Tulle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayConvocate Context triple: [Bishop of Tulle, mayConvocate, diocesan synod in Tulle]
-
A.
decidesToConvene
Indicates that an entity makes a decision to bring a group together for a meeting or assembly.
-
B.
convenesUnder
Indicates that an entity holds or conducts a meeting, session, or gathering under the authority, auspices, or framework of another entity or arrangement.
-
C.
convenesIf
Indicates that one entity brings others together for a meeting or assembly when certain conditions are met.
-
D.
convenes
Indicates bringing people or groups together to formally meet, discuss, or deliberate on a particular matter.
-
E.
canConvoke
chosen
Indicates that one entity has the authority or ability to formally call another entity or group together for a meeting or assembly.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc0982c8190916f9905ddb5e575 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.