Triple
T2282746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nymphs of Greek mythology |
E51317
|
entity |
| Predicate | mortality |
P24966
|
FINISHED |
| Object | Immortal or long-lived |
—
|
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 or long-lived | Statement: [Nymphs of Greek mythology, mortality, Immortal or long-lived]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mortality Context triple: [Nymphs of Greek mythology, mortality, Immortal or long-lived]
-
A.
mortalityRate
Indicates the proportion of individuals in a defined population that die within a specified time period.
-
B.
death
Indicates the event or state in which an entity ceases to live or exist, marking the end of its biological or functional processes.
-
C.
deathStatus
chosen
Indicates whether an entity is alive, dead, or in another specified state related to mortality.
-
D.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
E.
causeOfDeath
Indicates the specific factor, event, or condition that directly resulted in 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc21d6d748190980128c1bc5b9621 |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.