Triple
T31106927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outpost 32 |
E792817
|
entity |
| Predicate | dangerToWorld |
P171156
|
FINISHED |
| Object | potential release of King Ghidorah |
—
|
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: potential release of King Ghidorah | Statement: [Outpost 32, dangerToWorld, potential release of King Ghidorah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dangerToWorld Context triple: [Outpost 32, dangerToWorld, potential release of King Ghidorah]
-
A.
dangerWarning
Indicates that one entity issues or represents a warning about potential danger associated with another entity or situation.
-
B.
dangerousWhen
Indicates that one entity becomes harmful, risky, or unsafe under the conditions or in the presence of another entity or situation.
-
C.
threatToHumans
Indicates that the subject poses or represents a potential danger, harm, or risk to humans.
-
D.
isHazardTo
Indicates that one entity poses a potential source of danger, harm, or risk to another entity.
-
E.
isInDanger
Indicates that an entity is exposed to a significant risk of harm, loss, or adverse consequences.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c6e0b888190a417ae712c42db0d |
completed | May 3, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f69c2127088190ae92c72461576d3b |
completed | May 3, 2026, 12:51 a.m. |
Created at: April 29, 2026, 9:03 p.m.