Triple
T33049876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danaid trilogy |
E845693
|
entity |
| Predicate | survivalStatusOfTheDanaids |
P176387
|
FINISHED |
| Object | fragmentary or lost |
—
|
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: fragmentary or lost | Statement: [Danaid trilogy, survivalStatusOfTheDanaids, fragmentary or lost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivalStatusOfTheDanaids Context triple: [Danaid trilogy, survivalStatusOfTheDanaids, fragmentary or lost]
-
A.
survivalStatusOfTheSuppliants
Indicates the survival outcome or current life-or-death status of the suppliants in relation to a particular event or situation.
-
B.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
C.
survivesBy
Indicates that one entity continues to live or exist after another entity has died or ceased to exist.
-
D.
survivesShipwreck
Indicates that an entity continues to live or remain alive after experiencing a shipwreck.
-
E.
survivedBy
Indicates that one entity continues to live or exist after the death or end of another entity.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e029f0f88190b1f88d82a4a2cabd |
completed | May 3, 2026, 5:42 a.m. |
Created at: May 1, 2026, 1:24 a.m.