Triple
T36409380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Samuel Loomis |
E896834
|
entity |
| Predicate | triesToStop |
P185457
|
FINISHED |
| Object | Michael Myers |
—
|
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: Michael Myers | Statement: [Dr. Samuel Loomis, triesToStop, Michael Myers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triesToStop Context triple: [Dr. Samuel Loomis, triesToStop, Michael Myers]
-
A.
triesToTake
Indicates an attempt by one entity to take possession or control of another entity or resource, regardless of whether the attempt succeeds.
-
B.
triesToSave
Indicates an entity is making an effort or taking action with the intention of rescuing or preserving another entity or situation from harm, loss, or failure.
-
C.
triesToUse
Indicates an entity’s attempt or effort to make use of another entity, regardless of whether the use is successful.
-
D.
stoppedBy
Indicates that one entity causes another entity to cease moving, operating, or continuing an action.
-
E.
triesToExpose
Indicates an attempt by one entity to reveal, uncover, or make known information, intentions, or characteristics of another entity or situation.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.