Triple
T28950498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usher family |
E730999
|
entity |
| Predicate | hasLastHeir |
P177468
|
FINISHED |
| Object | Roderick Usher |
—
|
NE NERFINISHED |
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: Roderick Usher | Statement: [Usher family, hasLastHeir, Roderick Usher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLastHeir Context triple: [Usher family, hasLastHeir, Roderick Usher]
-
A.
lastHeir
chosen
Indicates that one entity is the final remaining heir in a line of succession to another entity’s estate, title, or inheritance.
-
B.
hasSuccession
Indicates that one entity follows or replaces another in a sequence, order, or position, forming a succession relationship between them.
-
C.
hasHeirApparentFunction
Indicates that an entity has a designated heir apparent role or function assigned to it.
-
D.
lastLegitimateMaleHeirOf
Indicates that one entity is the final male descendant in a legitimate line of succession or inheritance from another entity.
-
E.
hasLegalSuccessor
Indicates that one entity is the legally recognized successor or inheritor of another entity’s rights, obligations, or status.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 28, 2026, 8:43 a.m.