Triple
T29992734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | positronium |
E761922
|
entity |
| Predicate | annihilatesInto |
P168339
|
FINISHED |
| Object | photons |
—
|
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: photons | Statement: [positronium, annihilatesInto, photons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annihilatesInto Context triple: [positronium, annihilatesInto, photons]
-
A.
extinguishes
Indicates that one entity causes another entity (such as a flame, light, or process) to cease, end, or be put out.
-
B.
typeOfDestruction
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
-
C.
isEliminatedPrimarilyBy
Indicates that one entity serves as the main means or pathway by which another entity is removed, cleared, or disposed of.
-
D.
aimsToEliminate
Indicates an intention or directed effort by one entity to remove, destroy, or completely get rid of another entity or condition.
-
E.
abolishesBody
Indicates that one entity formally ends, eliminates, or does away with another entity or institutional body.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6791c8e088190a0766badc1d3b5cd |
completed | May 2, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:39 p.m.