Triple
T17862389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | corbomite bluff |
E446105
|
entity |
| Predicate | threatEffect |
P77465
|
FINISHED |
| Object | discourages enemy attack |
—
|
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: discourages enemy attack | Statement: [corbomite bluff, threatEffect, discourages enemy attack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatEffect Context triple: [corbomite bluff, threatEffect, discourages enemy attack]
-
A.
threat
Indicates a relationship where one entity expresses or poses potential harm, danger, or negative consequences toward another entity.
-
B.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
C.
threatDisplay
chosen
Indicates a behavior or signal by one entity intended to warn, intimidate, or deter another entity without immediate physical attack.
-
D.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
-
E.
perceivedThreat
Indicates that one entity regards another entity or situation as potentially harmful, dangerous, or adverse.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e49790ea148190b7a966812d44f430 |
completed | April 19, 2026, 8:51 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.