Triple
T791546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Fowell Buxton |
E16924
|
entity |
| Predicate | createdBaronet |
P19336
|
FINISHED |
| Object | 1840 |
—
|
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: 1840 | Statement: [Thomas Fowell Buxton, createdBaronet, 1840]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdBaronet Context triple: [Thomas Fowell Buxton, createdBaronet, 1840]
-
A.
baronetageCreationPurpose
Indicates the purpose or reason for which a particular baronetage title was created.
-
B.
dateOfKnighthood
Indicates the specific date on which an individual was formally granted knighthood.
-
C.
hereditaryPeerage
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
-
D.
dateOfElevationToPeerage
Indicates the specific date on which an individual was formally elevated to a rank of nobility or peerage.
-
E.
confersKnighthood
Indicates that one entity formally grants the status or title of knighthood to another entity.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a798c7608190b9c79c52a1fe0859 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50ef72c819084ffe9f31dbd0262 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a62b497081909503c8d30c7ce1db |
completed | March 1, 2026, 8:48 p.m. |
Created at: March 1, 2026, 7:38 p.m.