Triple
T34704911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Schleswig |
E1000474
|
entity |
| Predicate | reAnnexedBy |
P960
|
FINISHED |
| Object | Nazi Germany |
E1491
|
NE 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: Nazi Germany | Statement: [North Schleswig, reAnnexedBy, Nazi Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reAnnexedBy Context triple: [North Schleswig, reAnnexedBy, Nazi Germany]
-
A.
annexedBy
chosen
Indicates that one entity has been incorporated into and brought under the control or sovereignty of another entity.
-
B.
annexedAs
Indicates that one entity has been incorporated into and made a formal part of another entity, typically losing its prior independent status.
-
C.
annexedDuring
Indicates that one entity was formally incorporated into and brought under the control of another entity during a specified time period.
-
D.
annex
Indicates the act of formally incorporating one entity, typically a territory, into the domain or control of another.
-
E.
partialAnnexationBy
Indicates a relationship where one entity has annexed or incorporated only a portion of another entity’s territory, authority, or structure, rather than taking it over in full.
- F. None of above.
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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3752ecdc4c8190ad85108298505b00 |
completed | June 21, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.