Triple
T3921486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermium |
E88968
|
entity |
| Predicate | wasFirstIdentifiedIn |
P3985
|
FINISHED |
| Object | Ivy Mike thermonuclear test debris |
—
|
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: Ivy Mike thermonuclear test debris | Statement: [Fermium, wasFirstIdentifiedIn, Ivy Mike thermonuclear test debris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFirstIdentifiedIn Context triple: [Fermium, wasFirstIdentifiedIn, Ivy Mike thermonuclear test debris]
-
A.
wasFirstObservedIn
Indicates that an entity was initially noticed, recorded, or detected at a particular time or place.
-
B.
wasDiscoveredAt
chosen
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
C.
discoveryDate
Indicates the date on which something was first discovered or identified.
-
D.
wasDiscoveredIn
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
E.
firstDescribedAs
Indicates the original way or terms in which something was initially characterized, named, or documented.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.