Triple
T31105012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayt |
E792769
|
entity |
| Predicate | eventuallyBecomes |
P153109
|
FINISHED |
| Object | Duncan Idaho (restored personality) |
E224786
|
NE 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: Duncan Idaho (restored personality) | Statement: [Hayt, eventuallyBecomes, Duncan Idaho (restored personality)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventuallyBecomes Context triple: [Hayt, eventuallyBecomes, Duncan Idaho (restored personality)]
-
A.
eventuallyIn
Indicates that one entity will, at some later time or in the long run, come to be located in, belong to, or be contained within another entity or state.
-
B.
eventuallyOverrunBy
Indicates that one entity is ultimately defeated, overwhelmed, or taken over by another entity or force after some passage of time.
-
C.
eventualSuccessor
Indicates that one entity will become the successor of another at some later point in time, rather than immediately.
-
D.
eventuallyBefriends
Indicates that one entity, after some passage of time or intervening events, comes to form a friendly or amicable relationship with another entity.
-
E.
willBecome
chosen
Indicates that one entity is expected or destined to change state or identity into another entity in the future.
- F. None of above.
Provenance (4 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a294714fdc08190a1ddeb0dd4ad42f1 |
completed | June 10, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 29, 2026, 9:03 p.m.