Triple
T6041786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Consort of the United Kingdom |
E134561
|
entity |
| Predicate | holderDeathDateForAlbert |
P20
|
FINISHED |
| Object | 1861-12-14 |
—
|
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: 1861-12-14 | Statement: [Prince Consort of the United Kingdom, holderDeathDateForAlbert, 1861-12-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderDeathDateForAlbert Context triple: [Prince Consort of the United Kingdom, holderDeathDateForAlbert, 1861-12-14]
-
A.
dateOfDeath
chosen
Indicates the specific date on which an individual or entity died.
-
B.
yearOfDeath
Indicates the specific year in which an entity (typically a person or organism) died.
-
C.
deathDateEvent
Indicates the date on which a death occurred or a death-related event took place.
-
D.
notableBearerDeathYear
Indicates the year in which a notable bearer of the referenced name, title, or role died.
-
E.
approximateAgeAtDeath
Indicates the estimated age a person or entity was when they died, typically used when the exact age is unknown.
- 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056d11370819096ac35349bd91f4e |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049eb52a08190ac10fd703735f5aa |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.