Triple
T31581879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sardanapalus |
E805846
|
entity |
| Predicate | companionsAtDeath |
P134557
|
FINISHED |
| Object | concubines (legendary) |
—
|
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: concubines (legendary) | Statement: [Sardanapalus, companionsAtDeath, concubines (legendary)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companionsAtDeath Context triple: [Sardanapalus, companionsAtDeath, concubines (legendary)]
-
A.
wasCompanionOf
Indicates that one entity accompanied or associated closely with another, typically as a partner, ally, or fellow participant over some period of time.
-
B.
accompaniedByInAfterlife
chosen
Indicates that one entity is believed or depicted to be together with another entity in the afterlife.
-
C.
containsDeathOf
Indicates that the subject includes, depicts, or involves the death of the referenced entity.
-
D.
associatedWithDeathOf
Indicates a relationship where one entity is connected in some relevant way to the death of another entity, such as by involvement, causation, or contextual association.
-
E.
completionAfterDeathOf
Indicates that one event, process, or work is completed only after the death of a specified person.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 30, 2026, 10:23 p.m.