Triple
T31106923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outpost 32 |
E792817
|
entity |
| Predicate | hasContainmentSystem |
P92158
|
FINISHED |
| Object | cryogenic containment for 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: cryogenic containment for King Ghidorah | Statement: [Outpost 32, hasContainmentSystem, cryogenic containment for King Ghidorah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContainmentSystem Context triple: [Outpost 32, hasContainmentSystem, cryogenic containment for King Ghidorah]
-
A.
hasContainment
chosen
Indicates that one entity spatially or logically encloses, includes, or holds another within its bounds.
-
B.
hasCentralSystem
Indicates that an entity possesses or is associated with a primary controlling or coordinating system at its core.
-
C.
containmentStructure
Indicates that one entity serves as a physical or logical container or enclosing structure for another entity.
-
D.
hasParentSystem
Indicates that one system is hierarchically contained within or derived from another, which serves as its parent system.
-
E.
requiresContainment
Indicates that one entity must be physically or logically enclosed within another entity as a necessary condition or constraint.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01c51e2d088190b9dcce5b6de1cb9b |
completed | May 11, 2026, 12:01 p.m. |
| PD | Predicate disambiguation | batch_6a01c4c715a48190b7435de8a9d86fd4 |
completed | May 11, 2026, noon |
Created at: April 29, 2026, 9:03 p.m.