Triple
T33755405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Villiers, 1st Earl of Clarendon |
E864962
|
entity |
| Predicate | elevationToEarldom |
P184416
|
FINISHED |
| Object | 1776 |
—
|
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: 1776 | Statement: [Thomas Villiers, 1st Earl of Clarendon, elevationToEarldom, 1776]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationToEarldom Context triple: [Thomas Villiers, 1st Earl of Clarendon, elevationToEarldom, 1776]
-
A.
elevationToDukedomYear
Indicates the year in which an entity was elevated to the rank or status of a dukedom.
-
B.
elevatedToDukedom
Indicates that an entity has been raised or promoted to the rank or title of a dukedom.
-
C.
elevatedToPeerageFor
Indicates that a person was granted a noble title or peerage specifically as a result of, or in recognition for, a particular reason, action, or service.
-
D.
earldomHeldBy
Indicates that a specified earldom is or was held as a title by a particular person or entity.
-
E.
elevatedToDuchy
Indicates that a territory, region, or domain has been formally raised in rank or status to become a duchy.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: May 1, 2026, 1:45 a.m.