Triple
T9937990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | photon |
E194003
|
entity |
| Predicate | hasEnergyFormula |
P90763
|
FINISHED |
| Object | E = hν |
—
|
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: E = hν | Statement: [photon, hasEnergyFormula, E = hν]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnergyFormula Context triple: [photon, hasEnergyFormula, E = hν]
-
A.
hasEnergyFunction
Indicates that an entity is associated with, governed by, or characterized through a specific energy function.
-
B.
hasEnergyResource
Indicates that an entity possesses, controls, or is associated with a source of usable energy.
-
C.
hasEnergyRole
Indicates that one entity plays a specific functional role in the production, distribution, management, or use of energy in relation to another entity.
-
D.
energyExpression
chosen
Indicates that one entity represents, encodes, or specifies the energy (or energy-related formula/value) associated with another entity or system.
-
E.
hasOrderOfMagnitudeInJoules
Indicates that the quantity associated with an entity is approximately of a specified order of magnitude when measured in joules.
- 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.