Triple
T4399257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patriarch of Jerusalem |
E99571
|
entity |
| Predicate | relativeRankInPentarchy |
P7856
|
FINISHED |
| Object | fourth |
—
|
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 | Statement: [Patriarch of Jerusalem, relativeRankInPentarchy, fourth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeRankInPentarchy Context triple: [Patriarch of Jerusalem, relativeRankInPentarchy, fourth]
-
A.
rankInPentarchy
chosen
Indicates the relative hierarchical position an entity holds within the structure of the pentarchy.
-
B.
positionInTetrarchy
Indicates the specific role or rank an individual holds within a four-part governing or leadership structure (a tetrarchy).
-
C.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
-
D.
portRank
Indicates the relative importance or hierarchical ranking assigned to a port within a given system or context.
-
E.
orderRankWithinOrderOfTheBritishEmpire
Indicates the specific hierarchical rank an individual holds within the Order of the British Empire honors system.
- 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352cc4ab081908bc45d2f76cd4da8 |
completed | March 12, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:20 p.m.