Triple
T29454388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fear (1996 film) |
E747057
|
entity |
| Predicate | hasStalking |
P195183
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Fear (1996 film), hasStalking, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStalking Context triple: [Fear (1996 film), hasStalking, yes]
-
A.
isVictimOf
Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
-
B.
symbolicallyPursuedBy
Indicates that one entity is the target of another entity’s pursuit or quest in a figurative, metaphorical, or symbolic sense rather than a literal chase.
-
C.
hasPerpetratorStatement
Indicates that a statement has been made by the perpetrator regarding the related event or action.
-
D.
hasThreats
Indicates that one entity poses or is associated with potential danger, harm, or adverse consequences toward another entity.
-
E.
hasHomeInvasionPlot
Indicates that the work’s storyline includes a plot centered on an intrusion into a home or private dwelling, typically involving threat, conflict, or crime.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69fdb04d37288190969a0f39d92efb49 |
completed | May 8, 2026, 9:43 a.m. |
Created at: April 28, 2026, 3:35 p.m.