Triple
T30678821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kadašman-Enlil II |
E780993
|
entity |
| Predicate | kingNumberWithinDynasty |
P170010
|
FINISHED |
| Object | Later Kassite king |
—
|
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: Later Kassite king | Statement: [Kadašman-Enlil II, kingNumberWithinDynasty, Later Kassite king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kingNumberWithinDynasty Context triple: [Kadašman-Enlil II, kingNumberWithinDynasty, Later Kassite king]
-
A.
eraNumberInDynasty
Indicates that a specific era is identified by and associated with a particular numbered position within a dynasty.
-
B.
dynasticNumber
Indicates the ordinal position or identifying number assigned to a dynasty within a historical or genealogical sequence.
-
C.
reignInDynasty
Indicates that a person’s reign or rule occurs within the context of a specific dynasty.
-
D.
eraSequenceWithinDynasty
Indicates that one historical era occurs in a specific ordered position relative to another era within the same dynasty.
-
E.
rankWithinImperialFamily
Indicates the hierarchical position an individual holds within an imperial family relative to other family members.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b1a60488190a7c83edc951aa433 |
completed | May 2, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:32 p.m.