Triple
T36556214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eärnur |
E901704
|
entity |
| Predicate | directHeir |
P8423
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Eärnur, directHeir, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directHeir Context triple: [Eärnur, directHeir, none]
-
A.
lastHeir
Indicates that one entity is the final remaining heir in a line of succession to another entity’s estate, title, or inheritance.
-
B.
predecessorAsHeir
Indicates that one entity previously held the status of heir before being succeeded by another in that role.
-
C.
successorDesignationFor
Indicates the designation or identification of an entity that is intended to succeed or replace another entity in a given role, position, or function.
-
D.
agreedHeir
Indicates that one entity has been formally designated and accepted as the heir of another, typically through mutual agreement or legal arrangement.
-
E.
heirOf
chosen
Indicates that one entity is the legal or designated successor who inherits from another entity, typically upon that entity’s death or transfer of rights.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: May 3, 2026, 4:11 p.m.