Triple
T31045638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Southampton |
E791118
|
entity |
| Predicate | titleHolderSocialClass |
P108523
|
FINISHED |
| Object | English 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: English aristocracy | Statement: [Duke of Southampton, titleHolderSocialClass, English aristocracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderSocialClass Context triple: [Duke of Southampton, titleHolderSocialClass, English aristocracy]
-
A.
titleHolderSocialStatus
chosen
Indicates the social rank or class associated with the holder of a particular title within a given context.
-
B.
titleHolderClass
Indicates the class or category of entity that holds or bears a particular title.
-
C.
socialTitle
Indicates the formal social designation or honorific (such as Mr., Dr., Sir) associated with a person in relation to others.
-
D.
titleHolderType
Indicates the specific role or capacity in which an entity holds a title (e.g., owner, trustee, beneficiary).
-
E.
titleHolderNotably
Indicates that an entity holds a particular title in a way that is especially notable, distinguished, or worthy of specific mention.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: April 29, 2026, 8:59 p.m.