Triple
T18631056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laodice I |
E455416
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hellenistic royal consort |
C35038
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Hellenistic royal consort Context triple: [Laodice I, instanceOf, Hellenistic royal consort]
-
A.
Bithynian royal consort
A Bithynian royal consort is the spouse or recognized partner of a reigning king of Bithynia, holding a prominent position within the Hellenistic court and dynastic structure of the ancient Bithynian kingdom.
-
B.
Seleucid queen
chosen
A Seleucid queen is a royal woman of the Hellenistic Seleucid dynasty who held political, dynastic, and often diplomatic influence within the empire centered in Syria and Mesopotamia.
-
C.
Seleucid princess
A Seleucid princess is a royal woman of the Hellenistic Seleucid dynasty, often used as a political pawn through strategic marriages to secure alliances and legitimize territorial control.
-
D.
Byzantine empress consort
A Byzantine empress consort was the wife of a reigning Byzantine emperor who held significant ceremonial, political, and sometimes religious influence at the imperial court, though her authority was formally derived from her marriage rather than direct rule.
-
E.
Nabataean queen consort
A Nabataean queen consort is the wife of a reigning Nabataean king who holds ceremonial, dynastic, and sometimes political or religious influence within the Nabataean kingdom.
- F. None of above.
Provenance (1 batch)
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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.