Triple
T33149752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Buckinghamshire |
E848401
|
entity |
| Predicate | originalBaronyPeerage |
P1919
|
FINISHED |
| Object | Peerage of Great Britain |
E12433
|
NE 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: Peerage of Great Britain | Statement: [Earl of Buckinghamshire, originalBaronyPeerage, Peerage of Great Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBaronyPeerage Context triple: [Earl of Buckinghamshire, originalBaronyPeerage, Peerage of Great Britain]
-
A.
createdBaronOrBaronessOf
Indicates that one entity granted or established the noble title of baron or baroness for another entity.
-
B.
baronetcyOf
Indicates a hereditary title or rank of baronet held by or associated with a particular person, family, or lineage.
-
C.
regionOfPeerage
chosen
Indicates the geographic region or territorial area associated with a particular peerage title or rank.
-
D.
hereditaryPeerage
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
-
E.
isAmongOldestBaronies
Indicates that the barony is one of the earliest-established or longest-standing baronies within a given set or region.
- F. None of above.
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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0249374a8c8190ab19002a123da439 |
completed | May 11, 2026, 9:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3525bc4868819083b20bc3839649be |
completed | June 19, 2026, 11:19 a.m. |
| PD | Predicate disambiguation | batch_6a02486194b08190a489ae3a8f4a59a9 |
completed | May 11, 2026, 9:21 p.m. |
Created at: May 1, 2026, 1:28 a.m.