Triple
T31129864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Falmagne |
E793470
|
entity |
| Predicate | outcomeForBrabantForces |
P19109
|
FINISHED |
| Object | defeat |
—
|
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: defeat | Statement: [Battle of Falmagne, outcomeForBrabantForces, defeat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForBrabantForces Context triple: [Battle of Falmagne, outcomeForBrabantForces, defeat]
-
A.
resultOfSiege
Indicates that one entity is the outcome or consequence produced by a siege conducted against another entity.
-
B.
resultInArdennes
Indicates that one event, action, or condition leads to or causes an outcome specifically occurring in the Ardennes region.
-
C.
aimOfFrancoBatavianForces
Indicates that the specified objective or goal is the intended aim pursued by the Franco-Batavian forces.
-
D.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
E.
largerForceDefeated
Indicates that in a conflict or contest, the side with the numerically or materially larger force was ultimately defeated by its opponent.
- 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 29, 2026, 9:05 p.m.