Triple
T36546731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atani |
E901158
|
entity |
| Predicate | mortalityContrastedWith |
P54687
|
FINISHED |
| Object | Elvish immortality |
—
|
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: Elvish immortality | Statement: [Atani, mortalityContrastedWith, Elvish immortality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mortalityContrastedWith Context triple: [Atani, mortalityContrastedWith, Elvish immortality]
-
A.
mortalityRate
Indicates the proportion of individuals in a defined population that die within a specified time period.
-
B.
mortalStatus
chosen
Indicates the state or condition of an entity with respect to being mortal, immortal, or otherwise subject to death.
-
C.
earlyDeath
Indicates that an entity dies sooner than is typical or expected within a given context or population.
-
D.
associatedWithMortal
Indicates a relationship where an entity is connected or linked in some way to a mortal being (a being subject to death).
-
E.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.