Triple
T20663021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellie Cavanaugh |
E507805
|
entity |
| Predicate | timeFrameOfAction |
P302
|
FINISHED |
| Object | years after her sister’s murder |
—
|
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: years after her sister’s murder | Statement: [Ellie Cavanaugh, timeFrameOfAction, years after her sister’s murder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeFrameOfAction Context triple: [Ellie Cavanaugh, timeFrameOfAction, years after her sister’s murder]
-
A.
timeFrameSpecified
Indicates that a specific temporal period or duration has been explicitly defined or constrained for the related event, action, or relationship.
-
B.
frameOfAction
Indicates the contextual situation, setting, or circumstances within which an action or event takes place.
-
C.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
D.
timeframeOfCrimes
Indicates the period or span of time during which the crimes occurred or were committed.
-
E.
timeframeApproximate
Indicates that the time period associated with an event or relation is not exact but only roughly or loosely specified.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2f4872481908858eb88ce89dd47 |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.