Triple
T26827771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beren |
E675416
|
entity |
| Predicate | returnedFromDeath |
P138907
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Beren, returnedFromDeath, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedFromDeath Context triple: [Beren, returnedFromDeath, yes]
-
A.
returnInRevival
Indicates that an entity comes back or is brought back during a revival event or period.
-
B.
revivedAfter
Indicates that one entity comes back to life or is restored to a living or active state after a period of being dead, inactive, or nonfunctional, following another event or time point.
-
C.
returnedFromExile
Indicates that an entity has come back to its original place or community after a period of being exiled.
-
D.
returnsFromPresumedDeathIn
chosen
Indicates that an entity, previously believed to be dead, comes back and reappears in a specified context, place, or time.
-
E.
afterDeath
Indicates that one event, state, or condition occurs subsequent to and as a result of 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 4:59 a.m.