Triple
T1698774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giray |
E36720
|
entity |
| Predicate | dynasticPrinciple |
P31298
|
FINISHED |
| Object | agnatic seniority |
—
|
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: agnatic seniority | Statement: [Giray, dynasticPrinciple, agnatic seniority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticPrinciple Context triple: [Giray, dynasticPrinciple, agnatic seniority]
-
A.
dynasticType
Indicates the specific kind or category of dynastic relationship or succession pattern that applies between ruling entities or lineages.
-
B.
dynasticStatus
Indicates the relationship between an entity and a ruling dynasty, such as membership in, association with, or status within that dynastic line.
-
C.
dynasticStrategy
Indicates a relationship where an entity deliberately plans or manages succession, alliances, or power transfers across generations to maintain or enhance a ruling lineage or family’s influence.
-
D.
dynasticOrigin
Indicates the historical dynasty or ruling family from which an entity originates or descends.
-
E.
dynasticRole
Indicates the specific position, function, or status an entity holds within a dynasty or hereditary ruling line.
- F. None of above. chosen
Provenance (4 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf169da888190b3aa334752f1952b |
completed | March 6, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69aa61b8ce348190b46154af0b041ff0 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69aaf16865488190a76577b36760dc7a |
completed | March 6, 2026, 3:23 p.m. |
Created at: March 4, 2026, 7:30 p.m.