Triple
T33049875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danaid trilogy |
E845693
|
entity |
| Predicate | survivalStatusOfTheEgyptians |
P176096
|
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, survivalStatusOfTheEgyptians, fragmentary or lost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivalStatusOfTheEgyptians Context triple: [Danaid trilogy, survivalStatusOfTheEgyptians, fragmentary or lost]
-
A.
broughtToEgypt
Indicates that one entity caused another entity to be taken or transported to Egypt.
-
B.
conquestOfEgypt
Indicates the act or historical event of militarily subjugating and taking control of Egypt by another power.
-
C.
casualtiesEgyptianSide
Indicates the number of people killed or injured who belong to, or are counted as part of, the Egyptian side in a conflict or incident.
-
D.
EgyptRole
Indicates that an entity holds a specific role, function, or capacity in relation to Egypt.
-
E.
associatedWithPharaoh
Indicates a relationship in which an entity has a connection, link, or involvement with a pharaoh, such as through service, rule, influence, or historical association.
- 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_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:24 a.m.