Triple
T16974524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Tarutino |
E411774
|
entity |
| Predicate | FrenchAllyForce |
P70976
|
FINISHED |
| Object | Polish troops |
—
|
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: Polish troops | Statement: [Battle of Tarutino, FrenchAllyForce, Polish troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FrenchAllyForce Context triple: [Battle of Tarutino, FrenchAllyForce, Polish troops]
-
A.
FrenchUnit
chosen
Indicates that a unit or entity is associated with France, typically by origin, affiliation, or national identity.
-
B.
FrenchOperation
Indicates an operation, mission, or activity that is conducted by, under the authority of, or primarily involving France or French entities.
-
C.
FrenchRole
Indicates a role or position that an entity holds specifically within a French context (e.g., in France or related to French institutions, culture, or language).
-
D.
FrenchCasualties
Indicates that the relationship specifies the number or extent of casualties suffered by French forces in a given event or context.
-
E.
FrenchCommander
Indicates that an entity serves as a military commander associated with France.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d18300c8819080c8bf19962754ba |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:31 a.m.