Triple
T22090832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ghoul (Fallout TV series) |
E545906
|
entity |
| Predicate | longevityReason |
P122976
|
FINISHED |
| Object | ghoul physiology slows aging |
—
|
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: ghoul physiology slows aging | Statement: [The Ghoul (Fallout TV series), longevityReason, ghoul physiology slows aging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longevityReason Context triple: [The Ghoul (Fallout TV series), longevityReason, ghoul physiology slows aging]
-
A.
reasonForImmortality
Indicates that one entity specifies the cause, source, or mechanism by which another entity possesses immortality.
-
B.
lifespan
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
C.
humanLifespanTrend
Indicates how the typical length of human life changes over time or across different conditions.
-
D.
causeOfImmortality
chosen
Indicates that the subject is the reason or source for the object's immortality.
-
E.
lifetimeInGenerations
Indicates the number of successive generations over which something (e.g., an effect, trait, or validity) persists or remains applicable.
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e53dfc81909858cdad8b09c5fb |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.