Triple
T24997240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schleswig plebiscites |
E625604
|
entity |
| Predicate | outcomeForDenmark |
P154057
|
FINISHED |
| Object | reunification with North Schleswig |
—
|
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: reunification with North Schleswig | Statement: [Schleswig plebiscites, outcomeForDenmark, reunification with North Schleswig]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForDenmark Context triple: [Schleswig plebiscites, outcomeForDenmark, reunification with North Schleswig]
-
A.
outcomeForSweden
Indicates the resulting effect, consequence, or result that a situation, event, or action has specifically in relation to Sweden.
-
B.
impactOnDenmark
chosen
Indicates a relationship where an action, event, or entity produces an effect or consequence specifically on Denmark.
-
C.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
D.
outcomeForStralsund
Indicates the result, consequence, or effect that an event, action, or situation has specifically for Stralsund.
-
E.
strengthDenmark
Indicates a measure or characterization of Denmark’s power, influence, or robustness in a given context.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 6:04 a.m.