Triple
T17422007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henrik, Prince Consort of Denmark |
E423639
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Henrik |
—
|
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: Henrik | Statement: [Henrik, Prince Consort of Denmark, givenName, Henrik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Henrik Context triple: [Henrik, Prince Consort of Denmark, givenName, Henrik]
-
A.
Henrik
chosen
Henrik is the given name of the renowned Norwegian mathematician Niels Henrik Abel, known for his pioneering work in algebra and analysis.
-
B.
Søren
Søren is a masculine given name of Scandinavian origin, most famously borne by the Danish philosopher Søren Kierkegaard.
-
C.
Fredrik
Fredrik is a masculine given name of Scandinavian origin, commonly used in Norway, Sweden, and Denmark.
-
D.
Vilhelm
Vilhelm is a masculine given name of Germanic origin, related to William and common in various Scandinavian and European countries.
-
E.
Halvard
Halvard is a masculine given name of Scandinavian origin, particularly common in Norway.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44237f2cc819083ca0e7e00d828fb |
completed | April 19, 2026, 2:47 a.m. |
Created at: April 10, 2026, 5:46 a.m.