Triple
T2812436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen |
E54201
|
entity |
| Predicate | inheritsTitleBy |
P23689
|
FINISHED |
| Object | Hereditary succession |
—
|
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 succession | Statement: [Queen, inheritsTitleBy, Hereditary succession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inheritsTitleBy Context triple: [Queen, inheritsTitleBy, Hereditary succession]
-
A.
inheritsTitle
chosen
Indicates that one entity receives and assumes a formal title or rank previously held by another entity, typically through succession or inheritance.
-
B.
successorTitle
Indicates the title or position that directly follows and replaces a previous one in a sequence or succession.
-
C.
heldTitleFrom
Indicates that an entity possessed or held a particular title starting from a specified point in time.
-
D.
inheritedFrom
Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
-
E.
heldTitleByRightOfMother
Indicates that an individual holds a title or rank derived through their mother’s hereditary rights or 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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde4a31d081909377044d5ff791b0 |
completed | March 7, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69abdd0740208190911dc9c9546a79ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.