Triple
T27713868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb of Richard III |
E698764
|
entity |
| Predicate | commemoratesDynasty |
P167785
|
FINISHED |
| Object | House of York |
—
|
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: House of York | Statement: [Tomb of Richard III, commemoratesDynasty, House of York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commemoratesDynasty Context triple: [Tomb of Richard III, commemoratesDynasty, House of York]
-
A.
prominentDynasty
Indicates that a dynasty holds significant historical, political, or cultural importance relative to other dynasties.
-
B.
nativeDynasty
Indicates that a dynasty is indigenous to, or originally from, the place or polity it rules or is associated with.
-
C.
coronatedDynasty
Indicates that a particular dynasty was formally installed or crowned as the ruling house, typically through a coronation event.
-
D.
veneratedInDynasty
Indicates that an entity was revered, honored, or held in high esteem during a specific historical dynasty.
-
E.
depictsDynasty
Indicates that one entity visually represents or portrays a particular dynasty.
- F. None of above. chosen
Provenance (4 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 27, 2026, 3:03 p.m.