Triple
T30643767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Cholmondeley |
E780063
|
entity |
| Predicate | higherRankAssociated |
P88112
|
FINISHED |
| Object | Marquess of Cholmondeley |
—
|
NE NERFINISHED |
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: Marquess of Cholmondeley | Statement: [Baron Cholmondeley, higherRankAssociated, Marquess of Cholmondeley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherRankAssociated Context triple: [Baron Cholmondeley, higherRankAssociated, Marquess of Cholmondeley]
-
A.
higherRankHas
chosen
Indicates that one entity holds a higher rank or hierarchical position than another entity.
-
B.
higherRankDescription
Indicates that one entity holds a superior or more senior rank or status compared to another entity.
-
C.
associatedWithRank
Indicates a relationship where an entity is linked to a specific rank, level, or hierarchical position.
-
D.
higherTierAuthority
Indicates that one entity holds a superior or higher-ranking level of authority or control over another entity.
-
E.
higherAspectAssociatedWith
Indicates that one aspect or level of something is linked or connected to a corresponding higher-level aspect.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 29, 2026, 8:29 p.m.