Triple
T528832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Parliament |
E10983
|
entity |
| Predicate | rankInPeerage |
P3782
|
FINISHED |
| Object | lowest rank of the Scottish peerage |
—
|
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: lowest rank of the Scottish peerage | Statement: [Lord of Parliament, rankInPeerage, lowest rank of the Scottish peerage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankInPeerage Context triple: [Lord of Parliament, rankInPeerage, lowest rank of the Scottish peerage]
-
A.
rankRelativeToPeerage
Indicates how an entity’s hierarchical rank compares to that of a specified peer or peer group within a defined ranking system.
-
B.
rankInBritishPeerageSystem
Indicates the specific noble title or level an entity holds within the hierarchical structure of the British peerage system.
-
C.
typeOfPeerage
chosen
Indicates the specific rank or category within a system of peerage that a given title or noble status belongs to.
-
D.
regionOfPeerage
Indicates the geographic region or territorial area associated with a particular peerage title or rank.
-
E.
hereditaryPeerage
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d39b4c81909f265b3501b5ec1d |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f01ac3ec8190a94a05955532c7fa |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.