Triple
T30390394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesse Tuck |
E773064
|
entity |
| Predicate | offersImmortalityTo |
P62993
|
FINISHED |
| Object | Winnie Foster |
—
|
NE NERFINISHED |
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: Winnie Foster | Statement: [Jesse Tuck, offersImmortalityTo, Winnie Foster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersImmortalityTo Context triple: [Jesse Tuck, offersImmortalityTo, Winnie Foster]
-
A.
attemptedToMakeImmortal
Indicates that one entity tried, but did not necessarily succeed, to cause another entity to become immortal.
-
B.
deniedImmortalityBy
Indicates that one entity refused, prevented, or revoked the possibility of immortality for another entity.
-
C.
immortality
Indicates that an entity possesses the quality of never dying or ceasing to exist, persisting indefinitely through time.
-
D.
sharesImmortalityWith
chosen
Indicates that one entity grants or mutually possesses an immortal or deathless state together with another entity.
-
E.
offeredToDeity
Indicates that something is presented or dedicated as an offering to a deity.
- 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_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 29, 2026, 8:02 p.m.