Triple
T1028488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Fleurus (1794) |
E22193
|
entity |
| Predicate | decisive |
P24171
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Battle of Fleurus (1794), decisive, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisive Context triple: [Battle of Fleurus (1794), decisive, true]
-
A.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
-
B.
determined
Indicates that an entity has firmly decided on a course of action or conclusion, typically after consideration or effort.
-
C.
decisionMaking
Indicates the process by which an entity evaluates options and selects a course of action among alternatives.
-
D.
decisionEffect
Indicates that one decision leads to, influences, or determines a particular outcome or consequence.
-
E.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b95d35888190a20593a278175df7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7276180819085c6b23501a6a6e0 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b95bb5908190ad1d5f5e0d8f664d |
completed | March 1, 2026, 10:10 p.m. |
Created at: March 1, 2026, 7:41 p.m.