Triple
T6290120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tolstoy |
E140994
|
entity |
| Predicate | hasAncestralStatus |
P55649
|
FINISHED |
| Object | hereditary nobility |
—
|
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: hereditary nobility | Statement: [Tolstoy, hasAncestralStatus, hereditary nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralStatus Context triple: [Tolstoy, hasAncestralStatus, hereditary nobility]
-
A.
ancestralStatus
chosen
Indicates that one entity holds a particular ancestral or lineage-based relationship or status in relation to another entity.
-
B.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
C.
hasAncestor
Indicates that one entity is an ancestor (direct or indirect, such as a parent, grandparent, etc.) of another entity in a genealogical or hierarchical lineage.
-
D.
inheritanceStatus
Indicates the type or condition of inheritance rights or succession status that applies between related parties.
-
E.
hasAncestralEvent
Indicates that an entity is associated with a past ancestral occurrence or event in its 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_69c008cdf2ac8190bb640c94478fb4ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0641ca91481909d49b700cef93ffe |
completed | March 22, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69c060df0d8881908215575862ef6831 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:26 p.m.