Triple
T10121313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sue Snell |
E223295
|
entity |
| Predicate | unintentionallyContributesTo |
P1993
|
FINISHED |
| Object | prom night tragedy |
—
|
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: prom night tragedy | Statement: [Sue Snell, unintentionallyContributesTo, prom night tragedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unintentionallyContributesTo Context triple: [Sue Snell, unintentionallyContributesTo, prom night tragedy]
-
A.
tributeTo
Indicates that one entity is created, given, or dedicated as a mark of respect, admiration, or honor toward another entity.
-
B.
contributeTo
chosen
Indicates that one entity provides support, resources, or effort that helps bring about, enhance, or maintain another entity, outcome, or state.
-
C.
tributeFrom
Indicates that one entity pays or provides tribute, often as a sign of submission or obligation, to another entity.
-
D.
typicalIntentionsInclude
Indicates that one entity’s usual or characteristic intentions encompass or include the other entity or action.
-
E.
notAbout
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd266b18c8190b35fe637c912e756 |
completed | April 2, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:04 p.m.