Triple
T34984252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H-bomb |
E1008897
|
entity |
| Predicate | hasFirstTestCountry |
P125100
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [H-bomb, hasFirstTestCountry, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstTestCountry Context triple: [H-bomb, hasFirstTestCountry, United States]
-
A.
hasFirstReportedCountry
Indicates the country where something (such as a case, event, or phenomenon) was first officially reported or documented.
-
B.
testedInCountry
chosen
Indicates that an entity has been tested or evaluated within the geographical boundaries or jurisdiction of a specified country.
-
C.
hasCountry
Indicates that one entity possesses, is associated with, or is located within a specific country.
-
D.
testDebutForCountry
Indicates the event in which an individual makes their first official test appearance representing a particular country.
-
E.
wasFirstPerformedInCountry
Indicates that an action, event, or work was first performed within the borders of a specified country.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffada24d188190a576a02dc280a7fb |
completed | May 9, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69ffad46d6ac819081772f408b1389d5 |
completed | May 9, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:01 p.m.