Triple
T32433294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Know What You Did Last Summer (novel) |
E828784
|
entity |
| Predicate | timeBetweenAccidentAndThreats |
P174079
|
FINISHED |
| Object | about one year |
—
|
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: about one year | Statement: [I Know What You Did Last Summer (novel), timeBetweenAccidentAndThreats, about one year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeBetweenAccidentAndThreats Context triple: [I Know What You Did Last Summer (novel), timeBetweenAccidentAndThreats, about one year]
-
A.
timeBetweenInjuryAndDeath
Indicates the duration of time that elapses between when an injury occurs and when death subsequently happens.
-
B.
timeAfterAttack
Indicates that a specified time point occurs after an attack event has taken place.
-
C.
laterThreat
Indicates that one entity poses a threat to another at a time subsequent to some referenced or initial point.
-
D.
timeAfterDisaster
Indicates that a specified time point occurs after the occurrence of a particular disaster event.
-
E.
timeHorizonOfImpact
Indicates the span of time over which an action, event, or factor is expected to produce its effects or consequences.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2b0108c81908aab3d55aaf9f8e5 |
completed | May 3, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:55 a.m.