Triple
T3543148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parysatis II |
E74932
|
entity |
| Predicate | possibleRoyalDescent |
P20125
|
FINISHED |
| Object | Achaemenid royal family |
—
|
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: Achaemenid royal family | Statement: [Parysatis II, possibleRoyalDescent, Achaemenid royal family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleRoyalDescent Context triple: [Parysatis II, possibleRoyalDescent, Achaemenid royal family]
-
A.
parentOfRoyalDescendants
Indicates being the parent of one or more individuals who are of royal descent.
-
B.
heritageLine
Indicates that one entity is a historical or traditional predecessor, lineage, or source from which the other entity derives or continues.
-
C.
royalTribe
Indicates that an entity belongs to, descends from, or is associated with a tribe that holds royal or ruling status.
-
D.
originCountryOfPaternalLine
Indicates the country from which a person’s paternal family line (through the father’s side) originates.
-
E.
dynasticOrigin
chosen
Indicates the historical dynasty or ruling family from which an entity originates or descends.
- 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_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbf752dd481909226044ffe595338 |
completed | March 8, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69adae15749881909b847c6ca73c934e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.