Triple
T8879339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Albemarle |
E211367
|
entity |
| Predicate | nobleRankWithinPeerage |
P80950
|
FINISHED |
| Object | below marquess and above viscount |
—
|
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: below marquess and above viscount | Statement: [Earl of Albemarle, nobleRankWithinPeerage, below marquess and above viscount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleRankWithinPeerage Context triple: [Earl of Albemarle, nobleRankWithinPeerage, below marquess and above viscount]
-
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.
nobleRankIn
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
-
C.
rankInBritishPeerageSystem
Indicates the specific noble title or level an entity holds within the hierarchical structure of the British peerage system.
-
D.
nobleRankInHierarchy
chosen
Indicates the relative position or level of a noble title within a structured hierarchy of ranks.
-
E.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
- 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_69ca838e78748190934d82db3104f855 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc614ad1908190a77808fcf7f3e531 |
completed | April 1, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:52 p.m.