Triple
T37533349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry FitzRoy, 12th Duke of Grafton |
E933121
|
entity |
| Predicate | holdsSeniorDukedomIn |
P126277
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [Henry FitzRoy, 12th Duke of Grafton, holdsSeniorDukedomIn, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holdsSeniorDukedomIn Context triple: [Henry FitzRoy, 12th Duke of Grafton, holdsSeniorDukedomIn, United Kingdom]
-
A.
holdsPremierDukedom
chosen
Indicates that an entity holds the highest-ranking or most senior dukedom within a given nobility system.
-
B.
aristocraticTitleHeldBy
Indicates that a specific aristocratic or noble title is held or borne by a particular person.
-
C.
earldomHeldBy
Indicates that a specified earldom is or was held as a title by a particular person or entity.
-
D.
premierDukedomOf
Indicates that one dukedom holds the status of being the foremost or highest-ranking dukedom associated with a given entity (such as a person, title, or realm).
-
E.
hasNotableDukedom
Indicates that an entity holds or is associated with a dukedom that is considered historically or culturally significant.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.