Triple
T6436764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan (Eastern Orthodox Church) |
E129916
|
entity |
| Predicate | mayBeRankAbove |
P19077
|
FINISHED |
| Object | archbishop |
—
|
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: archbishop | Statement: [Metropolitan (Eastern Orthodox Church), mayBeRankAbove, archbishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeRankAbove Context triple: [Metropolitan (Eastern Orthodox Church), mayBeRankAbove, archbishop]
-
A.
isRankedAbove
chosen
Indicates that one entity holds a higher position or status in an ordered ranking than another entity.
-
B.
hasRankContext
Indicates that an entity’s rank or ordering is defined, interpreted, or constrained within a specific contextual framework or situation.
-
C.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
D.
isHighRanking
Indicates that an entity holds a position of relatively great authority, status, or seniority within a hierarchy or organization.
-
E.
isRank
Indicates that one entity serves as the rank, level, or hierarchical position associated with 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_69c0084caac48190a7bc2ad8ba44536f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c069622eb881908b40fc8079d312d6 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:45 p.m.