Triple
T38268789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syro-Malankara Catholic exarchates |
E1021144
|
entity |
| Predicate | canBeElevatedTo |
P88393
|
FINISHED |
| Object | eparchy |
—
|
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: eparchy | Statement: [Syro-Malankara Catholic exarchates, canBeElevatedTo, eparchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeElevatedTo Context triple: [Syro-Malankara Catholic exarchates, canBeElevatedTo, eparchy]
-
A.
mayBeUpgradedTo
Indicates that one entity is eligible or allowed to be changed into a higher, improved, or more advanced version represented by another entity.
-
B.
couldBePromotedTo
chosen
Indicates a potential or eligibility for one entity to be advanced or elevated to a higher role, status, or position relative to another.
-
C.
isElevatedAbove
Indicates that one entity is positioned at a higher vertical level or altitude than another entity.
-
D.
elevatedTo
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
E.
couldBePromotedFrom
Indicates that one entity has the potential or eligibility to be advanced in status, rank, or position from another specified 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffac35ac5481908b6bdfd5bbe8c76e |
completed | May 9, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69ffabbfd2548190964c851496bbbaee |
completed | May 9, 2026, 9:48 p.m. |
Created at: May 3, 2026, 4:30 p.m.