Triple
T25657293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danish Crown |
E643270
|
entity |
| Predicate | exercisedSovereigntyOver |
P70686
|
FINISHED |
| Object | Schleswig |
—
|
NE NERFINISHED |
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: Schleswig | Statement: [Danish Crown, exercisedSovereigntyOver, Schleswig]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exercisedSovereigntyOver Context triple: [Danish Crown, exercisedSovereigntyOver, Schleswig]
-
A.
sovereigntyExercisedThrough
Indicates that one entity’s sovereign authority or control is carried out, implemented, or manifested by means of another entity, mechanism, or arrangement.
-
B.
hasSovereignPowerOver
chosen
Indicates that one entity holds ultimate governing authority or supreme ruling power over another entity.
-
C.
affirmsSovereigntyOf
Indicates that one entity explicitly recognizes, supports, or upholds the sovereignty or sovereign authority of another entity.
-
D.
seatOfSovereignty
Indicates that a location serves as the primary center of governing authority or ruling power for a political entity.
-
E.
sovereigntyStatus
Indicates the degree and type of political independence or control an entity holds over its own territory and governance.
- 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 6:35 p.m.