Triple
T9628113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | metropolitans of the Ecumenical Patriarchate |
E232521
|
entity |
| Predicate | canHoldTitle |
P45332
|
FINISHED |
| Object | Metropolitan of a specific see |
—
|
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 of a specific see | Statement: [metropolitans of the Ecumenical Patriarchate, canHoldTitle, Metropolitan of a specific see]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canHoldTitle Context triple: [metropolitans of the Ecumenical Patriarchate, canHoldTitle, Metropolitan of a specific see]
-
A.
hasTitleHolder
Indicates that one entity is the current or designated holder of a specific title, position, or honor associated with another entity.
-
B.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
C.
mayBeTitled
chosen
Indicates that an entity can optionally bear or be assigned a particular title, but is not required to have it.
-
D.
heldTitleUntil
Indicates that an entity possessed or held a specific title or position continuously up to a particular end date or point in time.
-
E.
holderMayUseTitle
Indicates that the holder is permitted to use or bear a specified title.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9afeb64c8190be91024c2e9039d3 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.