Triple
T4111850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10 Cloverfield Lane |
E90192
|
entity |
| Predicate | outsideThreatDepictedAs |
P50110
|
FINISHED |
| Object | possible chemical or alien 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: possible chemical or alien attack | Statement: [10 Cloverfield Lane, outsideThreatDepictedAs, possible chemical or alien attack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outsideThreatDepictedAs Context triple: [10 Cloverfield Lane, outsideThreatDepictedAs, possible chemical or alien attack]
-
A.
facesThreat
Indicates that an entity is exposed to or confronted by a potential danger, risk, or harmful situation.
-
B.
recognizesThreat
Indicates that an entity identifies or acknowledges another entity or situation as a potential danger or source of harm.
-
C.
threatToHumans
Indicates that the subject poses or represents a potential danger, harm, or risk to humans.
-
D.
threatTypeAddressed
Indicates that a given action, measure, or entity is specifically intended to counter or mitigate a particular type of threat.
-
E.
threatType
chosen
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.