Triple
T27151526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tory ministry of Robert Harley |
E682401
|
entity |
| Predicate | conflictManaged |
P23081
|
FINISHED |
| Object | War of the Spanish Succession |
—
|
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: War of the Spanish Succession | Statement: [Tory ministry of Robert Harley, conflictManaged, War of the Spanish Succession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictManaged Context triple: [Tory ministry of Robert Harley, conflictManaged, War of the Spanish Succession]
-
A.
conflictTypeManaged
Indicates that a conflict has been addressed or handled through some form of management or resolution process.
-
B.
conflictPreserved
Indicates that an existing conflict or incompatibility between entities is maintained and not resolved or removed.
-
C.
conflictResolvedBy
chosen
Indicates that a conflict or dispute is settled or addressed through the actions, decisions, or intervention of a specified entity or process.
-
D.
conflictRecognized
Indicates that a conflict between parties, interests, or actions has been identified and acknowledged.
-
E.
conflictedBetween
Indicates being torn or uncertain between two or more options, positions, or commitments.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 9:14 a.m.