Triple
T28571133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melkite Greek Catholic bishops |
E723116
|
entity |
| Predicate | appoint |
P1649
|
FINISHED |
| Object | parish priests |
—
|
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: parish priests | Statement: [Melkite Greek Catholic bishops, appoint, parish priests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appoint Context triple: [Melkite Greek Catholic bishops, appoint, parish priests]
-
A.
appointmentBy
chosen
Indicates that one entity is appointed or designated to a role, position, or task by another entity.
-
B.
appointmentBody
Indicates that one entity serves as the main content or body text associated with a particular appointment.
-
C.
appointmentContext
Indicates the situational details or circumstances under which an appointment occurs, such as purpose, setting, or relevant conditions.
-
D.
appointmentTerm
Indicates the duration or specific period for which an appointment, position, or role is held.
-
E.
agendaForm
Indicates that an entity serves as or takes the form of an agenda, typically specifying the structure or format of planned items or discussions.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 28, 2026, 4:09 a.m.