Triple
T30565440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Ravensworth |
E777959
|
entity |
| Predicate | isHereditaryTitle |
P83369
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Baron Ravensworth, isHereditaryTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHereditaryTitle Context triple: [Baron Ravensworth, isHereditaryTitle, true]
-
A.
titleIsHereditary
chosen
Indicates that a title or rank is passed down through family lineage rather than being newly granted or earned each time.
-
B.
hereditaryTitleInheritance
Indicates that a hereditary title is passed from one individual to another according to established rules of succession.
-
C.
hereditaryTitleFor
Indicates that one entity is a hereditary title that is held by, or associated with, another entity, typically passed down through a family line.
-
D.
isHereditaryInPrinciple
Indicates that a characteristic, right, or status is, by its nature or underlying rules, intended to be passed down through inheritance.
-
E.
hasHereditaryChief
Indicates that an entity is led or governed by a chief whose position is inherited 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_69f2249ed41c8190b175170ecfd6e1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6890e7aec8190b0a79e08744acf5f |
completed | May 2, 2026, 11:30 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:21 p.m.