Triple
T24997241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schleswig plebiscites |
E625604
|
entity |
| Predicate | outcomeForGermany |
P158762
|
FINISHED |
| Object | retention of South 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: retention of South Schleswig | Statement: [Schleswig plebiscites, outcomeForGermany, retention of South Schleswig]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForGermany Context triple: [Schleswig plebiscites, outcomeForGermany, retention of South Schleswig]
-
A.
qualificationOutcomeForGermany
Indicates the result or status of a qualification process specifically as it applies to Germany.
-
B.
outcomeForPrussia
Indicates the result or consequence that an event, action, or situation has specifically for Prussia.
-
C.
objectiveGermany
Indicates that an entity has Germany as its objective, target, or goal in a given context.
-
D.
proposedActionByGermany
Indicates that Germany has suggested or put forward a specific action, plan, or measure to be considered or undertaken.
-
E.
strategyUsedByGermany
Indicates that a particular strategy is one that was employed or adopted by Germany.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 18, 2026, 6:04 a.m.