Triple
T20981293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oath of Tyndareus |
E516769
|
entity |
| Predicate | consequenceOfBreach |
P36372
|
FINISHED |
| Object | dishonor for the suitors |
—
|
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: dishonor for the suitors | Statement: [Oath of Tyndareus, consequenceOfBreach, dishonor for the suitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfBreach Context triple: [Oath of Tyndareus, consequenceOfBreach, dishonor for the suitors]
-
A.
violationConsequences
chosen
Indicates the negative outcomes, penalties, or repercussions that result from a violation of a rule, law, or agreement.
-
B.
breachedDuring
Indicates that one entity violated, broke, or failed to uphold another entity (such as a rule, contract, or security measure) within a specified time period or event.
-
C.
consequenceOfRevocation
Indicates that something occurs as a direct result of a prior revocation event or decision.
-
D.
riskIfBreached
Indicates that a breach of the referenced entity or condition would expose or create a potential risk or harm.
-
E.
hasConsequence
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbdea4988190bd091a5434acc376 |
completed | April 21, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:48 p.m.