Triple
T32023948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pound–Rebka experiment |
E817767
|
entity |
| Predicate | usedTransitionEnergy |
P179529
|
FINISHED |
| Object | 14.4 keV |
—
|
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: 14.4 keV | Statement: [Pound–Rebka experiment, usedTransitionEnergy, 14.4 keV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTransitionEnergy Context triple: [Pound–Rebka experiment, usedTransitionEnergy, 14.4 keV]
-
A.
hasEnergyTransition
Indicates a change in an entity’s primary energy source, technology, or system from one form or configuration to another over time.
-
B.
usesEnergyConversion
Indicates that an entity performs or involves a process where one form of energy is transformed into another to achieve a function or outcome.
-
C.
usesEnergyFrom
Indicates that one entity derives or consumes energy originating from another entity as its source.
-
D.
usesEnergy
Indicates that one entity consumes or relies on some form of energy to function, operate, or perform an action.
-
E.
usesEnergyForm
Indicates that an entity operates by drawing on or relying upon a particular form or type of energy.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: May 1, 2026, 12:17 a.m.