Triple
T20416052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berowne |
E500714
|
entity |
| Predicate | breaksVow |
P140056
|
FINISHED |
| Object | vow to abstain from women |
—
|
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: vow to abstain from women | Statement: [Berowne, breaksVow, vow to abstain from women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breaksVow Context triple: [Berowne, breaksVow, vow to abstain from women]
-
A.
breaksWith
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
-
B.
breaksUpIn
Indicates that one entity ends or dissolves a relationship or partnership with another entity.
-
C.
break
Indicates that one entity causes another entity to separate into pieces, stop functioning, or otherwise lose its normal integrity or continuity.
-
D.
brokenBy
Indicates that one entity causes the damage, destruction, or loss of functionality of another entity.
-
E.
brokenIn
Indicates that an object or system has become nonfunctional or damaged while located within or inside a particular place, context, or container.
- 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_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. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:30 a.m.