Triple
T2911249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lich (Adventure Time) |
E63685
|
entity |
| Predicate | formerIdentity |
P65
|
FINISHED |
| Object | Catalyst Comet essence |
—
|
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: Catalyst Comet essence | Statement: [The Lich (Adventure Time), formerIdentity, Catalyst Comet essence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerIdentity Context triple: [The Lich (Adventure Time), formerIdentity, Catalyst Comet essence]
-
A.
formerUser
Indicates that an entity was previously a user of another entity or system but is no longer one.
-
B.
formerName
chosen
Indicates that an entity was previously known by a different name in the past.
-
C.
subjectIdentity
Indicates that two or more references correspond to the same underlying entity or individual identity.
-
D.
formerMemberName
Indicates that the referenced name belongs to an entity that was previously a member of a particular group, organization, or body but is no longer one.
-
E.
formerType
Indicates that one entity previously had a certain type, role, or classification but no longer does.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0ea0ae4819096f17d74072b0b78 |
completed | March 7, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69abdd1b77608190b20fc078fdb85e64 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:11 p.m.