Triple
T25018318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Army |
E626201
|
entity |
| Predicate | roleInBattleOfGravelotte |
P165291
|
FINISHED |
| Object | central role |
—
|
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: central role | Statement: [Second Army, roleInBattleOfGravelotte, central role]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBattleOfGravelotte Context triple: [Second Army, roleInBattleOfGravelotte, central role]
-
A.
engagementResultAtBattleOfGravelotte
Indicates the outcome or result of a military engagement that took place during the Battle of Gravelotte.
-
B.
roleInGallicWars
Indicates the role or involvement an entity had in the events or campaigns of the Gallic Wars.
-
C.
limitedFrenchArmyTo
Indicates that an entity imposed restrictions or constraints on the size, capabilities, or actions of the French army relative to another entity or condition.
-
D.
roleInBattleOfSainteFoy
Indicates the specific role or involvement an entity had in the Battle of Sainte-Foy.
-
E.
roleInMalmedyMassacre
Indicates that an entity participated in, contributed to, or was otherwise involved in the Malmedy Massacre.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 18, 2026, 6:06 a.m.