Triple
T1250437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | reduced Planck constant |
E26861
|
entity |
| Predicate | relatedQuantity |
P4227
|
FINISHED |
| Object | quantum of action |
—
|
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: quantum of action | Statement: [reduced Planck constant, relatedQuantity, quantum of action]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedQuantity Context triple: [reduced Planck constant, relatedQuantity, quantum of action]
-
A.
quantifies
chosen
Indicates that one entity expresses or specifies the amount, number, or degree of another entity.
-
B.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
C.
relatedField
Indicates that one field, topic, or area of study is connected or relevant to another in subject matter or application.
-
D.
quantificationType
Indicates the specific kind or category of quantity or measurement being applied in a given context.
-
E.
relatedMIC
Indicates that there exists a relationship or connection between entities involving a MIC (Minimum Inhibitory Concentration) context, such as shared, comparable, or associated MIC values or measurements.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf84c73c8190bbb14265cd7ab6ae |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6b075881908e867c25b5080e25 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.