Triple
T19131245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan of Pergamon |
E468318
|
entity |
| Predicate | associatedWithCouncilParticipation |
P21722
|
FINISHED |
| Object | Ecumenical Patriarchate synods |
—
|
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: Ecumenical Patriarchate synods | Statement: [Metropolitan of Pergamon, associatedWithCouncilParticipation, Ecumenical Patriarchate synods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCouncilParticipation Context triple: [Metropolitan of Pergamon, associatedWithCouncilParticipation, Ecumenical Patriarchate synods]
-
A.
associatedWithCouncil
Indicates that an entity has a formal or recognized connection, involvement, or affiliation with a council.
-
B.
councilParticipation
chosen
Indicates that an entity takes part in, or is a member of, a council or governing body.
-
C.
relationToCouncil
Indicates the nature or type of connection an entity has with a council, such as membership, oversight, affiliation, or governance relationship.
-
D.
roleInCouncil
Indicates that an entity holds a specific position or function within a council or governing body.
-
E.
supportedCouncil
Indicates that an entity provided backing, endorsement, or assistance to a council.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3e980288190859026c0a0873fe2 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.