Triple
T37517752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ecumenical councils |
E932680
|
entity |
| Predicate | areConvokedBy |
P87355
|
FINISHED |
| Object | church authorities |
—
|
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: church authorities | Statement: [Ecumenical councils, areConvokedBy, church authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areConvokedBy Context triple: [Ecumenical councils, areConvokedBy, church authorities]
-
A.
puedenSerConvocadosPor
Indicates that one entity has the authority or ability to summon, call upon, or convene the other entity.
-
B.
canConvoke
chosen
Indicates that one entity has the authority or ability to formally call another entity or group together for a meeting or assembly.
-
C.
convenedFor
Indicates that an event, meeting, or gathering was brought together for a specific purpose, topic, or beneficiary.
-
D.
convenesOnRequestOf
Indicates that one entity is brought together or assembled at the initiative or formal request of another entity.
-
E.
wasConvenedBy
Indicates that an event, meeting, or gathering was formally called together, organized, or initiated by a specific agent or authority.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.