Triple
T27089167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McDreamy |
E686112
|
entity |
| Predicate | deathMedium |
P164311
|
FINISHED |
| Object | television series |
—
|
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: television series | Statement: [McDreamy, deathMedium, television series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathMedium Context triple: [McDreamy, deathMedium, television series]
-
A.
deathDescribedIn
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
-
B.
deathDescribedBy
Indicates that a death event is documented, characterized, or explained by a specific description or source.
-
C.
deathPractice
Indicates a relationship where an entity engages in practices, rituals, or preparations specifically related to death or dying.
-
D.
deathDescribedAs
Indicates that one entity characterizes, portrays, or refers to another entity’s death using a particular description, metaphor, or wording.
-
E.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
- F. None of above. chosen
Provenance (4 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 8:39 a.m.