Triple
T19175318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Orthodox primates |
E469422
|
entity |
| Predicate | areAssistedBy |
P48964
|
FINISHED |
| Object | synod of bishops |
—
|
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: synod of bishops | Statement: [Eastern Orthodox primates, areAssistedBy, synod of bishops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areAssistedBy Context triple: [Eastern Orthodox primates, areAssistedBy, synod of bishops]
-
A.
wasAssistedBy
chosen
Indicates that an entity carried out an action or achieved a result with the help or support of another entity.
-
B.
assistsWith
Indicates that one entity helps or supports another entity in performing or accomplishing a specific task, activity, or objective.
-
C.
canAssistIn
Indicates that one entity has the ability or capacity to help another entity perform, achieve, or carry out a particular task, goal, or activity.
-
D.
hasLifelinesOrAssists
Indicates that one entity provides lifelines, help, or supportive interventions to another entity.
-
E.
builtWithAssistanceFrom
Indicates that something was constructed, created, or developed with help, support, or collaboration from another party.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f166d3888190adaf6dc8531a8ed1 |
completed | April 20, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.