Triple
T20817833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | axe (1980 film) |
E512486
|
entity |
| Predicate | threatensFamilyUnit |
P141945
|
FINISHED |
| Object | Torrance family |
—
|
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: Torrance family | Statement: [axe (1980 film), threatensFamilyUnit, Torrance family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatensFamilyUnit Context triple: [axe (1980 film), threatensFamilyUnit, Torrance family]
-
A.
threatensMarriageOf
Indicates that one entity poses a risk or danger to the continuation, stability, or success of another entity’s marriage.
-
B.
threatToHumans
Indicates that the subject poses or represents a potential danger, harm, or risk to humans.
-
C.
threatenedVictim
Indicates that one entity has issued or posed a threat of harm or adverse consequences toward another entity.
-
D.
threatenedToKill
Indicates that one entity has made a threat or expressed an intention to kill another entity.
-
E.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2f429388190809dd532278fe310 |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:41 p.m.