Triple
T35171703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Saint-Denis (1567) |
E1015559
|
entity |
| Predicate | HuguenotCasualties |
P182904
|
FINISHED |
| Object | significant |
—
|
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: significant | Statement: [Battle of Saint-Denis (1567), HuguenotCasualties, significant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HuguenotCasualties Context triple: [Battle of Saint-Denis (1567), HuguenotCasualties, significant]
-
A.
HuguenotComposition
Indicates that something is composed of, created by, or fundamentally characterized by Huguenots or the Huguenot tradition.
-
B.
aimOfHuguenots
Indicates the goal or objective pursued by the Huguenots in a given context.
-
C.
RoyalistCasualties
Indicates the number or occurrence of casualties suffered by Royalist forces in a given conflict or event.
-
D.
FrenchCasualties
Indicates that the relationship specifies the number or extent of casualties suffered by French forces in a given event or context.
-
E.
martyredUnder
Indicates that an entity was killed or executed as a martyr during the rule, authority, or actions of another entity.
- 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f794f24e588190965e39b77534d53f |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 3, 2026, 4:02 p.m.