Triple
T8679840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaeger Program |
E206008
|
entity |
| Predicate | facesThreatFrom |
P73999
|
FINISHED |
| Object | Kaiju |
—
|
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: Kaiju | Statement: [Jaeger Program, facesThreatFrom, Kaiju]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facesThreatFrom Context triple: [Jaeger Program, facesThreatFrom, Kaiju]
-
A.
facesThreat
Indicates that an entity is exposed to or confronted by a potential danger, risk, or harmful situation.
-
B.
hasThreats
chosen
Indicates that one entity poses or is associated with potential danger, harm, or adverse consequences toward another entity.
-
C.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
D.
recognizesThreat
Indicates that an entity identifies or acknowledges another entity or situation as a potential danger or source of harm.
-
E.
threatFactors
Indicates that certain conditions, elements, or circumstances contribute to increasing the risk or likelihood of a harmful or adverse outcome.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae6d19c8190be003f7901c0468d |
completed | March 31, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.