Triple
T22301559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown Prince Carl of Denmark |
E551268
|
entity |
| Predicate | acceptedNorwegianThrone |
P25237
|
FINISHED |
| Object | 1905 |
—
|
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: 1905 | Statement: [Crown Prince Carl of Denmark, acceptedNorwegianThrone, 1905]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptedNorwegianThrone Context triple: [Crown Prince Carl of Denmark, acceptedNorwegianThrone, 1905]
-
A.
successorAsKingOfNorway
Indicates that one person becomes the next king of Norway following another person in the royal succession.
-
B.
acceptedThrone
chosen
Indicates that an entity has agreed to assume and take on the role and authority associated with a throne or rulership.
-
C.
coronationAsKingOfNorway
Indicates the event or relationship in which an individual is formally crowned and installed as the king of Norway.
-
D.
predecessorAsKingOfNorway
Indicates that one person previously held the position of King of Norway immediately before another person.
-
E.
successorAsKingOfDenmark
Indicates that one person becomes the next king of Denmark following another person in the royal succession.
- 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157245ee481909a7a3397de3ae355 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.