Triple
T30918808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarkel |
E787660
|
entity |
| Predicate | constructedUnderRuler |
P127076
|
FINISHED |
| Object | Khagan of the Khazars |
—
|
NE NERFINISHED |
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: Khagan of the Khazars | Statement: [Sarkel, constructedUnderRuler, Khagan of the Khazars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructedUnderRuler Context triple: [Sarkel, constructedUnderRuler, Khagan of the Khazars]
-
A.
constructedByRuler
chosen
Indicates that something was built, commissioned, or otherwise created under the authority or direction of a specific ruler.
-
B.
rulerDuringConstruction
Indicates that a particular person held ruling authority over a place or polity during the time a specific construction project was carried out.
-
C.
convertedUnderRuler
Indicates that one entity adopted a new religion, belief, or allegiance while under the authority, influence, or reign of a specified ruler.
-
D.
involvesRuler
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
-
E.
coRulerWith
Indicates that two or more entities share ruling authority over the same domain or polity at the same time.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 29, 2026, 8:51 p.m.