Triple
T1688117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Warsaw |
E36487
|
entity |
| Predicate | peakTerritorialExtentYear |
P18122
|
FINISHED |
| Object | 1810 |
—
|
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: 1810 | Statement: [Duchy of Warsaw, peakTerritorialExtentYear, 1810]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakTerritorialExtentYear Context triple: [Duchy of Warsaw, peakTerritorialExtentYear, 1810]
-
A.
peakTerritorialExtent
Indicates the maximum geographic area or territorial size that an entity controlled or occupied at the height of its expansion.
-
B.
peakYear
chosen
Indicates the year in which something reached its highest or most significant level, performance, or prominence.
-
C.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
D.
conquestYear
Indicates the year in which one entity successfully conquered or took control over another entity.
-
E.
peakTerritorialExtentUnder
Indicates that one entity reached its greatest territorial size or coverage while under the control, rule, or influence of another entity.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.