Triple
T134103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trinity test site, New Mexico |
E2713
|
entity |
| Predicate | firstOf |
P5008
|
FINISHED |
| Object | world’s first detonation of a nuclear weapon |
—
|
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: world’s first detonation of a nuclear weapon | Statement: [Trinity test site, New Mexico, firstOf, world’s first detonation of a nuclear weapon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOf Context triple: [Trinity test site, New Mexico, firstOf, world’s first detonation of a nuclear weapon]
-
A.
firstLetter
Indicates that one entity is the initial character or starting letter of another entity (typically a string or word).
-
B.
firstNode
Indicates that the subject is the initial or starting node in an ordered sequence, structure, or path.
-
C.
firstOffered
Indicates that one entity was the earliest or initial provider or proposer of something to another entity or context.
-
D.
recognizedFirstBy
Indicates that one entity was the earliest or initial recognizer, identifier, or acknowledger of another entity.
-
E.
firstOccupied
Indicates that an entity was the initial or earliest occupant of a particular place, position, or resource.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a25788b2688190a45b39447f702551 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a25650251c81908a6ea6368cd61198 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a256ea776081908fec36c3fdfb8d84 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.