Triple
T36571805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond |
E902138
|
entity |
| Predicate | endsConflict |
P4546
|
FINISHED |
| Object | Wars of the Roses (within the play’s narrative) |
—
|
NE NERFINISHED |
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: Wars of the Roses (within the play’s narrative) | Statement: [Richmond, endsConflict, Wars of the Roses (within the play’s narrative)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endsConflict Context triple: [Richmond, endsConflict, Wars of the Roses (within the play’s narrative)]
-
A.
endedConflict
chosen
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
B.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
C.
wonConflict
Indicates that one entity has prevailed over another in a conflict, contest, or struggle.
-
D.
supportedConflict
Indicates that one party provided assistance, resources, or endorsement to a side involved in a conflict or dispute.
-
E.
ledToConflict
Indicates that one event, action, or condition caused or significantly contributed to the emergence or escalation of a conflict between parties.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.