Triple
T18984707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Russell |
E464524
|
entity |
| Predicate | hasHereditaryPeerages |
P1913
|
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: [House of Russell, hasHereditaryPeerages, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHereditaryPeerages Context triple: [House of Russell, hasHereditaryPeerages, yes]
-
A.
hereditaryPeerage
chosen
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
-
B.
hasPeerageTitle
Indicates that an entity holds or is associated with a formal noble or aristocratic title within a peerage system.
-
C.
hasPeerageType
Indicates that an entity holds or is associated with a specific category or rank of peerage (noble title).
-
D.
linkedToPeerage
Indicates that one entity has an established connection or association with a system of peerage or noble titles.
-
E.
regionOfPeerage
Indicates the geographic region or territorial area associated with a particular peerage title or rank.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d65ec0bc8190b878252b1b4c3620 |
completed | April 20, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.