Triple
T17032050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscountess Goschen |
E413222
|
entity |
| Predicate | peerageClass |
P3782
|
FINISHED |
| Object | viscountcy |
—
|
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: viscountcy | Statement: [Viscountess Goschen, peerageClass, viscountcy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peerageClass Context triple: [Viscountess Goschen, peerageClass, viscountcy]
-
A.
typeOfPeerage
chosen
Indicates the specific rank or category within a system of peerage that a given title or noble status belongs to.
-
B.
peerageSystem
Indicates a hierarchical system of noble ranks and titles that defines relative status and privileges among members of a nobility.
-
C.
regionOfPeerage
Indicates the geographic region or territorial area associated with a particular peerage title or rank.
-
D.
peerageForLife
Indicates that an individual holds a noble title or rank granted for the duration of their lifetime only, without hereditary succession.
-
E.
hereditaryPeerage
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d9e7d481909d3d5bd241bd68f1 |
completed | April 18, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.