Triple
T14348046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Hohenzollern |
E355778
|
entity |
| Predicate | inheritsBy |
P3800
|
FINISHED |
| Object | primogeniture |
—
|
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: primogeniture | Statement: [Prince of Hohenzollern, inheritsBy, primogeniture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inheritsBy Context triple: [Prince of Hohenzollern, inheritsBy, primogeniture]
-
A.
inheritsSymbolFrom
Indicates that one entity derives or receives its symbolic representation or notation from another entity.
-
B.
inheritedFrom
chosen
Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
-
C.
derivedBy
Indicates that one entity is obtained, produced, or inferred from another through some transformation, process, or reasoning.
-
D.
isInherited
Indicates that one entity derives its characteristics, properties, or rights from another through an inheritance relationship.
-
E.
losesInheritanceThrough
Indicates that one party forfeits or is disqualified from receiving an inheritance as a consequence of another specified party or condition.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e8d081c8190ac805726a3e98f4c |
completed | April 14, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.