Triple
T20416148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dumaine |
E500716
|
entity |
| Predicate | breaksOath |
P1202
|
FINISHED |
| Object | by falling in love with Katherine |
—
|
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: by falling in love with Katherine | Statement: [Dumaine, breaksOath, by falling in love with Katherine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breaksOath Context triple: [Dumaine, breaksOath, by falling in love with Katherine]
-
A.
penaltyForBreakingOath
Indicates the punishment or negative consequence imposed when an oath is violated.
-
B.
oath
chosen
Indicates a formal, binding promise or pledge made by one party to uphold certain duties, truths, or obligations, often under conditions of solemnity or authority.
-
C.
brokeTreatyWith
Indicates that one party violated the terms of a formal agreement or treaty it had with another party.
-
D.
breaksWith
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
-
E.
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.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a4437448190b07b6e6e3de5830f |
completed | April 20, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:30 a.m.