Triple
T33149751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Buckinghamshire |
E848401
|
entity |
| Predicate | originalBaronyCreationDate |
P197251
|
FINISHED |
| Object | 1728 |
—
|
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: 1728 | Statement: [Earl of Buckinghamshire, originalBaronyCreationDate, 1728]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBaronyCreationDate Context triple: [Earl of Buckinghamshire, originalBaronyCreationDate, 1728]
-
A.
dateOfCreationOfBarony
chosen
Indicates the specific date on which a particular barony was formally created or established.
-
B.
dateOfBaronetcy
Indicates the date on which a person was granted or created a baronetcy title.
-
C.
historicBarony
Indicates that an entity has the status or role of a historic barony, i.e., it was once recognized as a baronial territorial or feudal jurisdiction.
-
D.
isAmongOldestBaronies
Indicates that the barony is one of the earliest-established or longest-standing baronies within a given set or region.
-
E.
creationOfDukedomDate
Indicates the date on which a particular dukedom was formally created or established.
- 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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0248062e608190aae1afdae38d2e5a |
completed | May 11, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_6a02465a0d38819084c3a6813fb943fc |
completed | May 11, 2026, 9:12 p.m. |
Created at: May 1, 2026, 1:28 a.m.