Triple
T1449701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marquess of Blandford |
E31260
|
entity |
| Predicate | isParliamentaryPeerage |
P20999
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Marquess of Blandford, isParliamentaryPeerage, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isParliamentaryPeerage Context triple: [Marquess of Blandford, isParliamentaryPeerage, false]
-
A.
hasPeerageType
Indicates that an entity holds or is associated with a specific category or rank of peerage (noble title).
-
B.
peerageSystem
Indicates a hierarchical system of noble ranks and titles that defines relative status and privileges among members of a nobility.
-
C.
isSovereignParliament
Indicates that a parliament holds ultimate legislative authority within its jurisdiction, not legally constrained by any higher lawmaking body.
-
D.
parliamentaryStatus
chosen
Indicates the relationship of whether and how an entity is formally recognized or holds standing within a parliamentary system or body.
-
E.
regionOfPeerage
Indicates the geographic region or territorial area associated with a particular peerage title or rank.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c55d923c8190957756f834f94462 |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c47a840c819083307a65c027a19e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.