Triple
T33149750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Buckinghamshire |
E848401
|
entity |
| Predicate | originalBaronetcyPeerage |
P84597
|
FINISHED |
| Object | Baronetage of England |
—
|
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: Baronetage of England | Statement: [Earl of Buckinghamshire, originalBaronetcyPeerage, Baronetage of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBaronetcyPeerage Context triple: [Earl of Buckinghamshire, originalBaronetcyPeerage, Baronetage of England]
-
A.
baronetcyOf
chosen
Indicates a hereditary title or rank of baronet held by or associated with a particular person, family, or lineage.
-
B.
createdBaronet
Indicates that one entity formally established or granted a baronetcy title to another entity.
-
C.
hereditaryPeerage
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
-
D.
createdBaronOrBaronessOf
Indicates that one entity granted or established the noble title of baron or baroness for another entity.
-
E.
dateOfBaronetcy
Indicates the date on which a person was granted or created a baronetcy title.
- 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_6a0245e917748190bf0a65db538aa66f |
completed | May 11, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_6a023f7cf7148190af5c2ea501511145 |
completed | May 11, 2026, 8:43 p.m. |
Created at: May 1, 2026, 1:28 a.m.