Triple
T134113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trinity test site, New Mexico |
E2713
|
entity |
| Predicate | resultOfExplosion |
P374
|
FINISHED |
| Object | formation of trinitite glass |
—
|
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: formation of trinitite glass | Statement: [Trinity test site, New Mexico, resultOfExplosion, formation of trinitite glass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfExplosion Context triple: [Trinity test site, New Mexico, resultOfExplosion, formation of trinitite glass]
-
A.
cityBombed
Indicates that a particular city was subjected to a bombing attack.
-
B.
result
chosen
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
C.
involvesProjectile
Indicates that the action or event includes the use, presence, or motion of a projectile as a key component of the interaction between entities.
-
D.
involvesParticleEjection
Indicates that the action or process includes the emission or release of particles from a source.
-
E.
damagedBy
Indicates that one entity has caused harm, impairment, or deterioration to another entity.
- 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_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. |
Created at: Feb. 28, 2026, 2:30 a.m.