Triple
T6961361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saxony |
E161375
|
entity |
| Predicate | statusDuringNapoleonicWars |
P19322
|
FINISHED |
| Object | initially allied with France |
—
|
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: initially allied with France | Statement: [Saxony, statusDuringNapoleonicWars, initially allied with France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusDuringNapoleonicWars Context triple: [Saxony, statusDuringNapoleonicWars, initially allied with France]
-
A.
statusDuringWar
chosen
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
B.
securityStatusDuringNapoleonExile
Indicates the security conditions or measures in place during the period of Napoleon’s exile.
-
C.
statusDuringWorldWarII
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
-
D.
warPeriod
Indicates a time span during which a state of war or armed conflict is ongoing between parties.
-
E.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
- 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6daf07e3481909aa79b8e0f1b1be7 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.