Triple
T8969542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friedland |
E214227
|
entity |
| Predicate | battleSecuredForNapoleon |
P85997
|
FINISHED |
| Object | strategic dominance in Central Europe |
—
|
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: strategic dominance in Central Europe | Statement: [Friedland, battleSecuredForNapoleon, strategic dominance in Central Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleSecuredForNapoleon Context triple: [Friedland, battleSecuredForNapoleon, strategic dominance in Central Europe]
-
A.
endTimeOfUseByNapoleon
Indicates the point in time when Napoleon’s use or control of something came to an end.
-
B.
securityStatusDuringNapoleonExile
Indicates the security conditions or measures in place during the period of Napoleon’s exile.
-
C.
startTimeOfUseByNapoleon
Indicates the point in time when Napoleon began using or employing something.
-
D.
NapoleonTitleWhileThere
Indicates that a specified title or rank was held by Napoleon during his presence at a particular place or in a particular context.
-
E.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
- 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_69ca839dbf608190a2f5990477115d29 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6765babc8190a4a3b79aa21047c8 |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5fcf24348190b6b845205161c0ee |
completed | March 31, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:01 p.m.