Triple
T9938000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | photon |
E194003
|
entity |
| Predicate | createdInProcess |
P1431
|
FINISHED |
| Object | atomic electronic transitions |
—
|
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: atomic electronic transitions | Statement: [photon, createdInProcess, atomic electronic transitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdInProcess Context triple: [photon, createdInProcess, atomic electronic transitions]
-
A.
createdProcess
Indicates that an entity is responsible for originating or bringing into existence a particular process.
-
B.
createdIn
chosen
Indicates that one entity was brought into existence, produced, or originated within the context, location, or time frame specified by another entity.
-
C.
usedProcess
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
D.
createdWith
Indicates that something was produced, built, or brought into existence using a particular tool, method, material, or resource.
-
E.
createdTo
Indicates that one entity was brought into existence, produced, or designed specifically for the purpose, use, or function of 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5e64760819094f599f158d32f33 |
completed | April 2, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:44 p.m.