Triple
T10316363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wrottesley family |
E242024
|
entity |
| Predicate | hasHereditaryPeerage |
P26323
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Wrottesley family, hasHereditaryPeerage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHereditaryPeerage Context triple: [Wrottesley family, hasHereditaryPeerage, yes]
-
A.
hereditaryPeerage
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
-
B.
hasPeerageType
chosen
Indicates that an entity holds or is associated with a specific category or rank of peerage (noble title).
-
C.
hasHereditaryChief
Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
-
D.
hasHereditaryOffice
Indicates that an entity holds an office or position that is passed down through family lineage rather than acquired by election, appointment, or merit.
-
E.
isNotPeerage
Indicates that the entity does not belong to any recognized peerage or noble rank within a hierarchical social or nobility system.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f4f354819080b4ed4bc61bdff6 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:49 a.m.