Triple
T18897676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Kimbolton |
E462250
|
entity |
| Predicate | historicalPeerage |
P64418
|
FINISHED |
| Object | English peerage system |
—
|
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: English peerage system | Statement: [Baron Kimbolton, historicalPeerage, English peerage system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeerage Context triple: [Baron Kimbolton, historicalPeerage, English peerage system]
-
A.
hereditaryPeerage
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
-
B.
peerageSystem
Indicates a hierarchical system of noble ranks and titles that defines relative status and privileges among members of a nobility.
-
C.
regionOfPeerage
Indicates the geographic region or territorial area associated with a particular peerage title or rank.
-
D.
peerageCreated
Indicates that a noble title or rank within a peerage system has been formally established or conferred.
-
E.
linkedToPeerage
chosen
Indicates that one entity has an established connection or association with a system of peerage or noble titles.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c52689308190b2e5ca163b1f6cd1 |
completed | April 20, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.