Triple
T844831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orthodox Church of Jerusalem |
E18254
|
entity |
| Predicate | rankInHonor |
P337
|
FINISHED |
| Object | fourth among Eastern Orthodox Churches |
—
|
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: fourth among Eastern Orthodox Churches | Statement: [Orthodox Church of Jerusalem, rankInHonor, fourth among Eastern Orthodox Churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankInHonor Context triple: [Orthodox Church of Jerusalem, rankInHonor, fourth among Eastern Orthodox Churches]
-
A.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
-
B.
honorLevel
chosen
Indicates the degree or status of respect, distinction, or recognition accorded to an entity relative to others.
-
C.
awardOrRanking
Indicates that there is an award, honor, or ranking status conferred on or associated with an entity.
-
D.
honors
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
-
E.
honourType
Indicates the specific category or classification of an honour or award associated with an 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac09249c8190a8099b94a3c9e2cc |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7f396c8190aa8b8dfbe0b4f732 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.