Triple
T30572417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ötüken |
E778153
|
entity |
| Predicate | corePowerBaseOf |
P112282
|
FINISHED |
| Object | Göktürk Khaganate |
—
|
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: Göktürk Khaganate | Statement: [Ötüken, corePowerBaseOf, Göktürk Khaganate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corePowerBaseOf Context triple: [Ötüken, corePowerBaseOf, Göktürk Khaganate]
-
A.
hasPowerBase
chosen
Indicates that an entity derives support, influence, or authority from a particular group, location, or resource that serves as its primary base of power.
-
B.
coreBasedOn
Indicates that one entity is fundamentally derived from, built upon, or primarily based on another entity.
-
C.
hasCorePower
Indicates that an entity possesses a primary or fundamental power, ability, or capability that defines its essential function or role.
-
D.
primaryPower
Indicates that one entity serves as the main or dominant source of power or energy for another entity.
-
E.
keyPower
Indicates that an entity possesses a primary or controlling power, authority, or influence over another entity or process.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6891430e88190b817a955536b4afd |
completed | May 2, 2026, 11:30 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:22 p.m.