Triple
T34704914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Schleswig |
E1000474
|
entity |
| Predicate | reAnnexationStatus |
P182441
|
FINISHED |
| Object | de facto |
—
|
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: de facto | Statement: [North Schleswig, reAnnexationStatus, de facto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reAnnexationStatus Context triple: [North Schleswig, reAnnexationStatus, de facto]
-
A.
annexationStatus
Indicates the current state or condition of one territory being formally incorporated into another sovereign entity.
-
B.
statusAfterAnnexation
Indicates the legal or political condition an entity holds following its annexation by another entity.
-
C.
reAnnexationContext
Indicates the circumstances or background conditions under which a territory is re-annexed or brought back under a previous authority’s control.
-
D.
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.
-
E.
annexedAs
Indicates that one entity has been incorporated into and made a formal part of another entity, typically losing its prior independent status.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f78d7211a48190bfb59c406f0bf12f |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c6014e08190864785a4fe3e8e73 |
completed | May 3, 2026, 5:56 p.m. |
Created at: May 3, 2026, 3:59 p.m.