Triple
T9151768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of Leeds |
E219602
|
entity |
| Predicate | usedByNobilityClass |
P9679
|
FINISHED |
| Object | British aristocracy |
—
|
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: British aristocracy | Statement: [Duchess of Leeds, usedByNobilityClass, British aristocracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByNobilityClass Context triple: [Duchess of Leeds, usedByNobilityClass, British aristocracy]
-
A.
usedByNobility
Indicates that something is employed, possessed, or utilized specifically by members of the nobility.
-
B.
nobilityClass
chosen
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
C.
usedByNobleFamily
Indicates that something is employed, possessed, or otherwise utilized by a noble family.
-
D.
nobilitySystem
Indicates a social or political structure in which individuals are ranked by hereditary titles or noble status.
-
E.
associatedWithNobilityConceptually
Indicates a conceptual or symbolic connection between something and nobility, such as aristocratic status, noble qualities, or related social class ideas.
- 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_69ca83e25418819093c6503deeaf30de |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca96cf4548190a3a45172f0e9d0ec |
completed | April 1, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.