Triple
T19369584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saxony–Poland–Lithuania |
E484495
|
entity |
| Predicate | secondUnionPeriodStart |
P62192
|
FINISHED |
| Object | 1709 |
—
|
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: 1709 | Statement: [Saxony–Poland–Lithuania, secondUnionPeriodStart, 1709]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondUnionPeriodStart Context triple: [Saxony–Poland–Lithuania, secondUnionPeriodStart, 1709]
-
A.
secondPhaseStartDate
Indicates the date on which the second phase of a process, project, or activity begins.
-
B.
personalUnionPeriod
Indicates a time span during which two or more distinct political entities are joined under a single ruler in a personal union.
-
C.
secondTermStartYear
Indicates the calendar year in which an entity’s second term in a role, office, or position begins.
-
D.
shareHistoricalUnionPeriod
Indicates that two entities were part of the same political or administrative union during an overlapping historical time period.
-
E.
personalUnionStartTime
chosen
Indicates the point in time when a personal union between entities begins.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619af33e481908643f8beb2f498dc |
completed | April 20, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.