Triple
T5097964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin Patriarchate of Antioch |
E114912
|
entity |
| Predicate | patriarchRank |
P61086
|
FINISHED |
| Object | patriarch |
—
|
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: patriarch | Statement: [Latin Patriarchate of Antioch, patriarchRank, patriarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patriarchRank Context triple: [Latin Patriarchate of Antioch, patriarchRank, patriarch]
-
A.
patriarch
Indicates a relationship where one entity serves as the male head or senior father-figure authority over a family, clan, or lineage of other entities.
-
B.
patriarchTitle
Indicates that one entity holds the role or title of patriarch in relation to another entity.
-
C.
patriarchFeatured
Indicates that a patriarch is prominently highlighted or given special emphasis in relation to something (such as a work, event, or context).
-
D.
recognizesPatriarch
Indicates that one entity acknowledges or accepts another entity as a patriarchal authority or head.
-
E.
patriarchate
Indicates a relationship in which authority, leadership, or control is held predominantly or exclusively by men, especially fathers or male elders, over a group, community, or institution.
- F. None of above. chosen
Provenance (4 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7567d21081909227ed8f08b74c71 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd738ac2e0819099c06cdcc5e21d28 |
completed | March 20, 2026, 4:19 p.m. |
Created at: March 20, 2026, 1:40 p.m.