Triple
T23117148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Edinburgh |
E576786
|
entity |
| Predicate | isHereditaryInPrinciple |
P150968
|
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: [Duke of Edinburgh, isHereditaryInPrinciple, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHereditaryInPrinciple Context triple: [Duke of Edinburgh, isHereditaryInPrinciple, yes]
-
A.
isHereditaryWithRespectTo
Indicates that a property, trait, or condition is passed down from ancestors to descendants according to genetic or lineage-based inheritance.
-
B.
hasHereditaryBasis
Indicates that a trait, condition, or characteristic is determined or influenced by genetic inheritance passed down through family lines.
-
C.
oftenHereditary
Indicates that the relationship or property typically passes from parents to offspring through genetic inheritance.
-
D.
hasHereditaryRights
Indicates that one entity possesses rights or privileges that are passed down through family lineage or inheritance from another entity.
-
E.
isHereditarySurname
Indicates that a surname is passed down through family lines across generations as part of hereditary naming traditions.
- F. None of above. chosen
Provenance (4 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_69e245f6c2e881909a228fdcfeb7c7d3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e4d095081908bad99fab6eaadd0 |
completed | April 29, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:59 p.m.