Triple
T23481025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Edward Morbius |
E570403
|
entity |
| Predicate | unwittinglyCreates |
P150475
|
FINISHED |
| Object | Id monster |
—
|
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: Id monster | Statement: [Dr. Edward Morbius, unwittinglyCreates, Id monster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unwittinglyCreates Context triple: [Dr. Edward Morbius, unwittinglyCreates, Id monster]
-
A.
intendedToCreate
Indicates that one entity performed an action or was designed with the purpose or goal of bringing another entity into existence or causing it to come about.
-
B.
airedCreatedBy
Indicates that the airing or broadcast of a work was created or produced by a specific agent or entity.
-
C.
involvesCreationOf
Indicates that one entity brings about, produces, or results in the creation of another entity.
-
D.
oftenCreatedBy
Indicates that something is frequently produced, generated, or brought into existence by a particular agent or cause.
-
E.
unexpectedConsequenceOf
chosen
Indicates that one event, action, or condition occurs as an unforeseen or unintended result of another.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a75002008190b02fbffd94e5e8b1 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:03 p.m.