Triple
T34704912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Schleswig |
E1000474
|
entity |
| Predicate | reAnnexationDate |
P9430
|
FINISHED |
| Object | 1940 |
—
|
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: 1940 | Statement: [North Schleswig, reAnnexationDate, 1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reAnnexationDate Context triple: [North Schleswig, reAnnexationDate, 1940]
-
A.
annexationDate
Indicates the date on which one entity formally annexed or incorporated another entity into its territory or jurisdiction.
-
B.
annexedDuring
Indicates that one entity was formally incorporated into and brought under the control of another entity during a specified time period.
-
C.
annexedInYear
chosen
Indicates that one entity was formally annexed or incorporated into another in the specified calendar year.
-
D.
retrocessionDate
Indicates the date on which rights, obligations, or control previously transferred are formally returned or reassigned back to the original party or another designated party.
-
E.
laterAnnexedTo
Indicates that one entity was annexed by another entity at a later point in time, after its initial status or affiliation.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 3:59 p.m.