Triple

T15016136
Position Surface form Disambiguated ID Type / Status
Subject W88 thermonuclear warhead E377963 entity
Predicate relativeSizeComparedToW76 P8238 FINISHED
Object more compact reentry body 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: more compact reentry body | Statement: [W88 thermonuclear warhead, relativeSizeComparedToW76, more compact reentry body]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relativeSizeComparedToW76
Context triple: [W88 thermonuclear warhead, relativeSizeComparedToW76, more compact reentry body]
  • A. scaleComparison
    Indicates a relationship where two or more entities are compared in terms of their size, magnitude, or scale relative to one another.
  • B. relativeSizeOnTethys
    Indicates how the size of one entity compares to another specifically in the context of Tethys.
  • C. relativeSizeInJapan
    Indicates how the size of one entity compares to another specifically within the context of Japan.
  • D. desiredSizeIndicates
    Indicates that one entity specifies or reflects the preferred or intended size of another entity.
  • E. hasRelativeSize chosen
    Indicates that one entity’s size is being compared to another entity’s size, expressing a relative rather than absolute magnitude.
  • 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_69d85cd3a3c881908c71fc424d459c17 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded7633fcc8190b2231f43252bc46f completed April 15, 2026, 12:10 a.m.
PD Predicate disambiguation batch_69de9a6531a88190acde65199a477350 completed April 14, 2026, 7:49 p.m.
Created at: April 10, 2026, 2:55 a.m.