Triple
T4393311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compton effect |
E99416
|
entity |
| Predicate | maximumWavelengthShift |
P46842
|
FINISHED |
| Object | 2 h / (m_e c) |
—
|
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: 2 h / (m_e c) | Statement: [Compton effect, maximumWavelengthShift, 2 h / (m_e c)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumWavelengthShift Context triple: [Compton effect, maximumWavelengthShift, 2 h / (m_e c)]
-
A.
maximumProtonEnergy
Indicates the highest energy value that protons can attain in a given system, process, or context.
-
B.
maximumMagnitude
chosen
Indicates the greatest absolute value or intensity that a quantity, measurement, or effect can reach within a given context.
-
C.
maximumReach
Indicates the greatest extent, distance, or limit that something can reach or influence within a given context.
-
D.
primaryWavelength
Indicates the main or dominant wavelength associated with an entity, such as the principal wavelength at which it emits, reflects, or operates.
-
E.
maximumWorkingDistance
Indicates the greatest allowable or effective distance at which the specified work, operation, or interaction can be performed.
- 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352a8862481909dc67abf42be6928 |
completed | March 12, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.