Triple
T30390494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miles Tuck |
E773067
|
entity |
| Predicate | hasImmortalityStatus |
P7319
|
FINISHED |
| Object | immortal |
—
|
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: immortal | Statement: [Miles Tuck, hasImmortalityStatus, immortal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImmortalityStatus Context triple: [Miles Tuck, hasImmortalityStatus, immortal]
-
A.
attemptedToMakeImmortal
Indicates that one entity tried, but did not necessarily succeed, to cause another entity to become immortal.
-
B.
becomesImmortalIn
Indicates that an entity transitions into a state of immortality within a specified context, time, or medium.
-
C.
immortality
chosen
Indicates that an entity possesses the quality of never dying or ceasing to exist, persisting indefinitely through time.
-
D.
isUndead
Indicates that an entity is no longer living in a natural sense but continues to exist through supernatural or unnatural means.
-
E.
hasRoleInImmunity
Indicates that an entity functions in or contributes to an immune-related process or mechanism.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 29, 2026, 8:02 p.m.