Triple
T13296364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Douglas, 1st Duke of Queensberry |
E316692
|
entity |
| Predicate | aristocraticTitleCreationDate |
P31263
|
FINISHED |
| Object | 1684 |
—
|
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: 1684 | Statement: [William Douglas, 1st Duke of Queensberry, aristocraticTitleCreationDate, 1684]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aristocraticTitleCreationDate Context triple: [William Douglas, 1st Duke of Queensberry, aristocraticTitleCreationDate, 1684]
-
A.
nobleTitleCreationDate
chosen
Indicates the date on which a particular noble title was formally created or granted.
-
B.
nobleTitleStartDate
Indicates the date on which an entity first acquired or began holding a particular noble title.
-
C.
aristocraticTitleCreationReason
Indicates the reason or circumstance under which an aristocratic title was created or granted.
-
D.
aristocraticTitlePassedTo
Indicates that an aristocratic title is transferred or inherited from one person to another.
-
E.
aristocraticTitleIn
Indicates that an entity holds or is associated with a specific aristocratic or noble title within a particular jurisdiction or context.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:28 p.m.