Triple
T24053460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish Pomerania |
E595725
|
entity |
| Predicate | finalCessionBy |
P154679
|
FINISHED |
| Object | Congress of Vienna |
—
|
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: Congress of Vienna | Statement: [Swedish Pomerania, finalCessionBy, Congress of Vienna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalCessionBy Context triple: [Swedish Pomerania, finalCessionBy, Congress of Vienna]
-
A.
finalDisposition
Indicates the ultimate outcome, status, or resolution assigned to an entity after all relevant processes or decisions are complete.
-
B.
finalHeld
Indicates that an entity ultimately retains possession or control of another entity at the conclusion of a process or event.
-
C.
finalRealization
Indicates the culminating recognition or understanding that occurs at the end of a process, event, or sequence of actions.
-
D.
finalRecord
Indicates that a record represents the last or ultimate version/state in a sequence or process.
-
E.
requiredCessionTo
Indicates that one entity must transfer or yield rights, control, or ownership to another entity as a necessary condition.
- 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9d4325c819080b878fe77280947 |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:21 p.m.