Triple
T31311796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Fontenoy (841) |
E798481
|
entity |
| Predicate | hasParentConflict |
P61381
|
FINISHED |
| Object | Carolingian civil war of 840–843 |
—
|
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: Carolingian civil war of 840–843 | Statement: [Battle of Fontenoy (841), hasParentConflict, Carolingian civil war of 840–843]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentConflict Context triple: [Battle of Fontenoy (841), hasParentConflict, Carolingian civil war of 840–843]
-
A.
hasRelatedConflict
chosen
Indicates that one entity is associated with another entity through a related or connected conflict, dispute, or incompatibility.
-
B.
hasConflictStatus
Indicates that there exists a state of conflict or dispute associated with the relationship between the involved entities.
-
C.
hasPrimaryConflictType
Indicates that an entity is associated with its main or most significant type of conflict among possible conflict categories.
-
D.
hasConflictCause
Indicates that one entity is the cause or source of a conflict involving another entity.
-
E.
hasOngoingConflict
Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: April 29, 2026, 9:15 p.m.