Triple
T16546131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belarus region |
E401946
|
entity |
| Predicate | partOfCampaignRoute |
P6309
|
FINISHED |
| Object | Napoleon’s advance toward Moscow |
—
|
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: Napoleon’s advance toward Moscow | Statement: [Belarus region, partOfCampaignRoute, Napoleon’s advance toward Moscow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfCampaignRoute Context triple: [Belarus region, partOfCampaignRoute, Napoleon’s advance toward Moscow]
-
A.
partOfCampaign
Indicates that an entity participates in, belongs to, or is included within a specific campaign.
-
B.
locationOfCampaign
Indicates the place or geographic area where a particular campaign is conducted or based.
-
C.
isPartOfRoute
chosen
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
D.
plannedCampaign
Indicates that an entity has designed and scheduled a campaign to be executed in the future.
-
E.
testCampaign
Indicates that an entity is involved in or associated with a campaign conducted for testing, experimentation, or evaluation purposes.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34562c30c81908d6318f359002ff2 |
completed | April 18, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.