Triple
T37859250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Brill (1643 raid) |
E944276
|
entity |
| Predicate | hasPartInConflict |
P35813
|
FINISHED |
| Object | First English Civil War |
—
|
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: First English Civil War | Statement: [Battle of Brill (1643 raid), hasPartInConflict, First English Civil War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartInConflict Context triple: [Battle of Brill (1643 raid), hasPartInConflict, First English Civil War]
-
A.
hasPartOfConflict
chosen
Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
-
B.
hasOngoingConflict
Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
-
C.
hasRelatedConflict
Indicates that one entity is associated with another entity through a related or connected conflict, dispute, or incompatibility.
-
D.
hasRoleInConflict
Indicates that an entity holds or held a specific role, position, or function within a particular conflict or dispute.
-
E.
hasSubjectConflictParticipatedIn
Indicates that a subject is involved in or has taken part in a particular conflict.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a006be462288190ae18e1567e2ad29f |
completed | May 10, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_6a0069e7a424819098d38458c3823605 |
completed | May 10, 2026, 11:20 a.m. |
Created at: May 3, 2026, 4:19 p.m.