Triple
T19369585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saxony–Poland–Lithuania |
E484495
|
entity |
| Predicate | secondUnionPeriodEnd |
P34836
|
FINISHED |
| Object | 1763 |
—
|
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: 1763 | Statement: [Saxony–Poland–Lithuania, secondUnionPeriodEnd, 1763]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondUnionPeriodEnd Context triple: [Saxony–Poland–Lithuania, secondUnionPeriodEnd, 1763]
-
A.
secondTermEnd
Indicates that the referenced time or event marks the conclusion of the second term in a sequence of terms.
-
B.
associatedPeriodEnd
chosen
Indicates the ending point or final date of the time period with which something is associated.
-
C.
finalPeriodAssociatedWith
Indicates that something is linked to or occurs during the last relevant time period in a sequence or lifecycle.
-
D.
secondPhaseEndTime
Indicates the time at which the second phase of a process or event concludes.
-
E.
secondRoundEndDate
Indicates the date on which the second round of an event, process, or activity concludes.
- 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.