Triple
T7396107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Vienna (1815) |
E170624
|
entity |
| Predicate | transfersTerritory |
P21042
|
FINISHED |
| Object | Norway from Denmark to Sweden |
—
|
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: Norway from Denmark to Sweden | Statement: [Treaty of Vienna (1815), transfersTerritory, Norway from Denmark to Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transfersTerritory Context triple: [Treaty of Vienna (1815), transfersTerritory, Norway from Denmark to Sweden]
-
A.
transferredRegion
chosen
Indicates that control, ownership, or responsibility for a geographic or administrative region has been moved from one entity to another.
-
B.
adminTerritory
Indicates that one entity serves as the administrative authority or governing jurisdiction over a specified territory.
-
C.
renamedTerritory
Indicates that an existing territory has been given a new official name, linking the former designation to its updated one.
-
D.
territoryUnifiedWith
Indicates that two or more territories have been politically or administratively merged into a single unified territorial entity.
-
E.
receivedTerritory
Indicates that one entity was granted or took possession of a territory from 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_69c68a5f04188190ac266569c9280347 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f248f79c819094b1d1e2c3d511d1 |
completed | March 27, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:09 p.m.