Triple
T3295592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambyses I |
E69206
|
entity |
| Predicate | pre-imperialRole |
P47814
|
FINISHED |
| Object | local king under Median overlordship |
—
|
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: local king under Median overlordship | Statement: [Cambyses I, pre-imperialRole, local king under Median overlordship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pre-imperialRole Context triple: [Cambyses I, pre-imperialRole, local king under Median overlordship]
-
A.
preMonarchicGovernment
Indicates that an entity has a form of government that existed before the establishment of a monarchy.
-
B.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
-
C.
earlierDynasty
Indicates that one dynasty chronologically precedes another in historical succession.
-
D.
preRomanStatus
Indicates the status or condition of an entity during the period before Roman rule or Roman cultural dominance.
-
E.
historicalEntityPredecessor
Indicates that one historical entity existed or held a role before another, serving as its predecessor in time or sequence.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb077c60c81909782be5202ce5a43 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:10 p.m.