Triple
T26194786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Stanley |
E655067
|
entity |
| Predicate | peerageContext |
P145458
|
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: [Lord Stanley, peerageContext, British aristocracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peerageContext Context triple: [Lord Stanley, peerageContext, British aristocracy]
-
A.
peerageSystem
Indicates a hierarchical system of noble ranks and titles that defines relative status and privileges among members of a nobility.
-
B.
peerageCreated
Indicates that a noble title or rank within a peerage system has been formally established or conferred.
-
C.
peerageForLife
Indicates that an individual holds a noble title or rank granted for the duration of their lifetime only, without hereditary succession.
-
D.
regionOfPeerage
Indicates the geographic region or territorial area associated with a particular peerage title or rank.
-
E.
countryOfPeerage
chosen
Indicates the country under whose nobility or peerage system a given title or peerage belongs.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60ca50d0081909d146f3c697227aa |
completed | May 2, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:46 p.m.