Triple
T3332795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monomakhovichi |
E70070
|
entity |
| Predicate | followsSuccessionPrinciple |
P8007
|
FINISHED |
| Object | rota system (ladder succession) |
—
|
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: rota system (ladder succession) | Statement: [Monomakhovichi, followsSuccessionPrinciple, rota system (ladder succession)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsSuccessionPrinciple Context triple: [Monomakhovichi, followsSuccessionPrinciple, rota system (ladder succession)]
-
A.
successorInPractice
Indicates that one entity has taken over the role, position, or function of another in actual practice, even if not formally or officially designated as its successor.
-
B.
hasSuccession
Indicates that one entity follows or replaces another in a sequence, order, or position, forming a succession relationship between them.
-
C.
successionOrder
Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
-
D.
successionPattern
chosen
Indicates the characteristic way in which one entity follows, replaces, or is ordered after another in a sequence or succession.
-
E.
successionDefinedBy
Indicates that the rules, order, or conditions of succession for one entity are determined or specified by another 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb194960081909333c855f06d8b03 |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42c2ba8819091136805ce17b39d |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.