Triple
T10968920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major Archbishop of Kyiv–Halych |
E259179
|
entity |
| Predicate | isLowerInRankThan |
P11456
|
FINISHED |
| Object | patriarch (in Catholic hierarchy) |
—
|
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 (in Catholic hierarchy) | Statement: [Major Archbishop of Kyiv–Halych, isLowerInRankThan, patriarch (in Catholic hierarchy)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLowerInRankThan Context triple: [Major Archbishop of Kyiv–Halych, isLowerInRankThan, patriarch (in Catholic hierarchy)]
-
A.
isRankedAbove
Indicates that one entity holds a higher position or status in an ordered ranking than another entity.
-
B.
lowerRank
chosen
Indicates that one entity holds an inferior or subordinate rank, status, or position relative to another entity.
-
C.
isRank
Indicates that one entity serves as the rank, level, or hierarchical position associated with another entity.
-
D.
isEntryLevelRankFor
Indicates that a rank represents the lowest or starting level within a particular role, position, or hierarchy.
-
E.
lowerOrEqualRankTitle
Indicates that one entity’s rank or title is lower than or equal to the rank or title of another entity.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7719800388190943a0bffa48a2731 |
completed | April 9, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69d72e8c27cc81908050590b7a04cafd |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:24 p.m.