Triple
T37533367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry FitzRoy, 12th Duke of Grafton |
E933121
|
entity |
| Predicate | hasAristocraticStatus |
P52082
|
FINISHED |
| Object | British peer |
—
|
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: British peer | Statement: [Henry FitzRoy, 12th Duke of Grafton, hasAristocraticStatus, British peer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAristocraticStatus Context triple: [Henry FitzRoy, 12th Duke of Grafton, hasAristocraticStatus, British peer]
-
A.
hasRelativeInAristocracy
Indicates that an entity has at least one relative who belongs to the aristocracy or noble class.
-
B.
aristocraticHouseStatus
Indicates the formal social or legal standing of an aristocratic house within a hierarchical nobility system.
-
C.
hasNobleStatus
chosen
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
D.
aristocraticTitleStatus
Indicates the status or condition of an entity’s aristocratic or noble title (e.g., whether and how the title is held, recognized, or used).
-
E.
aristocraticOrigin
Indicates that an entity originates from, or is derived from, an aristocratic or noble background.
- 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_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4:17 p.m.