Triple
T3948599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassandra |
E84806
|
entity |
| Predicate | statusAfterFallOfTroy |
P46175
|
FINISHED |
| Object | war prize of Agamemnon |
—
|
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: war prize of Agamemnon | Statement: [Cassandra, statusAfterFallOfTroy, war prize of Agamemnon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterFallOfTroy Context triple: [Cassandra, statusAfterFallOfTroy, war prize of Agamemnon]
-
A.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
B.
statusAfter1453
Indicates the status or condition of an entity after the year 1453, typically in contrast to its status before that date.
-
C.
afterConquest
chosen
Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
-
D.
postwarOutcome
Indicates the result or consequences that follow for a party or situation after a war has ended.
-
E.
statusAfterWWII
Indicates the condition, role, or classification an entity had following the end of World War II.
- 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_69aed934fbfc8190847068e4546de963 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa5afdc8190b709af2473d75d02 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8ed04e4819096bced8971cd888d |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:30 p.m.