Triple
T27098161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian Frederik Carl Georg Valdemar Axel |
E686364
|
entity |
| Predicate | adoptedRegnalName |
P25963
|
FINISHED |
| Object | Haakon VII |
—
|
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: Haakon VII | Statement: [Christian Frederik Carl Georg Valdemar Axel, adoptedRegnalName, Haakon VII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedRegnalName Context triple: [Christian Frederik Carl Georg Valdemar Axel, adoptedRegnalName, Haakon VII]
-
A.
tookRegnalName
chosen
Indicates that a person adopted and used a specific official regnal name upon assuming a throne or sovereign rulership.
-
B.
coronatedPersonRegnalName
Indicates the official regnal name that a person assumes upon being coronated.
-
C.
eraNameUsedDuringReign
Indicates that a particular era name was officially used throughout the duration of a ruler's reign.
-
D.
associatedTitleAfterEnthronement
Indicates the formal title or designation that is linked to an individual specifically after they have been enthroned or installed in an official position.
-
E.
coronatedNameAtBirth
Indicates that an entity’s coronation name is the same as their name at birth.
- 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:46 a.m.