Triple
T32342348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syriac Catholic Patriarch of Antioch |
E826351
|
entity |
| Predicate | higherOfficeThan |
P88112
|
FINISHED |
| Object | metropolitan |
—
|
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: metropolitan | Statement: [Syriac Catholic Patriarch of Antioch, higherOfficeThan, metropolitan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherOfficeThan Context triple: [Syriac Catholic Patriarch of Antioch, higherOfficeThan, metropolitan]
-
A.
office held level
Indicates the hierarchical level or rank at which an office or position is held within an organizational or governmental structure.
-
B.
higherRankHas
chosen
Indicates that one entity holds a higher rank or hierarchical position than another entity.
-
C.
hasElevatorOffice
Indicates that an office is equipped with or accessible via an elevator.
-
D.
hasUpperFloor
Indicates that one entity possesses or includes an upper floor relative to another level or reference point.
-
E.
upperLevels
Indicates that one entity occupies or corresponds to higher levels, tiers, or hierarchical positions relative to 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 1, 2026, 12:48 a.m.