Triple
T26351905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quemoy Crisis |
E662922
|
entity |
| Predicate | threatenedUseOf |
P161284
|
FINISHED |
| Object | nuclear weapons |
—
|
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: nuclear weapons | Statement: [Quemoy Crisis, threatenedUseOf, nuclear weapons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatenedUseOf Context triple: [Quemoy Crisis, threatenedUseOf, nuclear weapons]
-
A.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
B.
threatToHumans
Indicates that the subject poses or represents a potential danger, harm, or risk to humans.
-
C.
threatenedResponse
Indicates that one entity performs or communicates a response as a result of being threatened by another entity or situation.
-
D.
threatensToDestroy
Indicates that one entity has expressed an intention or warning that it will cause the complete ruin or elimination of another entity or object.
-
E.
threatenedToKill
Indicates that one entity has made a threat or expressed an intention to kill another entity.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 26, 2026, 10:45 p.m.