Triple
T34984254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H-bomb |
E1008897
|
entity |
| Predicate | hasFirstTestName |
P200849
|
FINISHED |
| Object | Ivy Mike |
—
|
NE NERFINISHED |
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: Ivy Mike | Statement: [H-bomb, hasFirstTestName, Ivy Mike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstTestName Context triple: [H-bomb, hasFirstTestName, Ivy Mike]
-
A.
hasTestNamedAfterHer
Indicates that a person is the namesake of a test, meaning a test is named in honor of or after her.
-
B.
hasFirstTestDate
Indicates that an entity is associated with the date on which its first test or testing event took place.
-
C.
hasFirstSunName
Indicates that an entity has a specific name assigned to it that is used or recognized during its first sun-related event or phase.
-
D.
hasFirstTerm
Indicates that an entity is associated with a specific first term in an ordered sequence, period, or series.
-
E.
hasFirstTerms
Indicates that one entity includes or is associated with the initial or earliest terms of another entity (such as a sequence, series, or agreement).
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffb1f0b03c81909ddb81f07ce74e88 |
completed | May 9, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ffb1662b2481908582e0612744f4c5 |
completed | May 9, 2026, 10:12 p.m. |
| PDg | Predicate description generation | batch_69ffb1f001948190a63c493b596a97b9 |
completed | May 9, 2026, 10:15 p.m. |
Created at: May 3, 2026, 4:01 p.m.