Triple
T34865193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skåneland |
E1004989
|
entity |
| Predicate | transferAdjustedBy |
P199381
|
FINISHED |
| Object | Treaty of Copenhagen (1660) |
—
|
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: Treaty of Copenhagen (1660) | Statement: [Skåneland, transferAdjustedBy, Treaty of Copenhagen (1660)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferAdjustedBy Context triple: [Skåneland, transferAdjustedBy, Treaty of Copenhagen (1660)]
-
A.
transferBetween
Indicates a movement or handover of something from one entity to another, typically changing its location, ownership, or control between them.
-
B.
transferAfter
Indicates that one entity transfers something to another entity only after a specified event or condition has occurred.
-
C.
transferImplementedBy
Indicates that a specific transfer process or specification is realized or carried out by a particular implementation or mechanism.
-
D.
transferType
Indicates the specific method or category of how something is transferred from one entity to another.
-
E.
transferPossibility
Indicates that it is possible for ownership, control, or rights over something to be transferred from one entity to another.
- F. None of above. chosen
Provenance (4 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
| PDg | Predicate description generation | batch_69ff32b6dd448190a7a6ebb76b99d4cc |
completed | May 9, 2026, 1:12 p.m. |
Created at: May 3, 2026, 4 p.m.