Triple
T5849456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Duke of Russia |
E129991
|
entity |
| Predicate | rankRelativeToTsar |
P50407
|
FINISHED |
| Object | below Emperor of Russia |
—
|
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: below Emperor of Russia | Statement: [Grand Duke of Russia, rankRelativeToTsar, below Emperor of Russia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankRelativeToTsar Context triple: [Grand Duke of Russia, rankRelativeToTsar, below Emperor of Russia]
-
A.
rankBeforeKingship
Indicates that one entity held a higher or earlier rank or status than another entity prior to that other entity attaining kingship.
-
B.
rankRelativeToPeerage
Indicates how an entity’s hierarchical rank compares to that of a specified peer or peer group within a defined ranking system.
-
C.
rankInPrincelyOrder
chosen
Indicates the position or level an entity holds within a specified princely order or hierarchy.
-
D.
rankInPentarchy
Indicates the relative hierarchical position an entity holds within the structure of the pentarchy.
-
E.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:55 p.m.