Triple
T27317611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viipuri Province |
E689389
|
entity |
| Predicate | territoryCededAfter |
P131500
|
FINISHED |
| Object | Winter War |
—
|
NE NERFINISHED |
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: Winter War | Statement: [Viipuri Province, territoryCededAfter, Winter War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territoryCededAfter Context triple: [Viipuri Province, territoryCededAfter, Winter War]
-
A.
countryCedingTerritory
Indicates that one country is formally transferring control or ownership of a portion of its territory to another entity.
-
B.
territoryAcquired
Indicates that one entity has gained control, ownership, or possession of a geographic area from another entity.
-
C.
annexedTerritory
Indicates that one political entity has formally incorporated another territory into its own sovereign domain.
-
D.
historicalSovereigntyEndedBy
Indicates that a former sovereignty or ruling authority over an entity came to an end as a result of the specified event, action, or successor power.
-
E.
wasCededAfter
chosen
Indicates that control or ownership of one entity was formally transferred to another entity following a specified event or point in time.
- 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 11:31 a.m.