Triple
T7229959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck–Einstein relation |
E154876
|
entity |
| Predicate | symbolForFrequency |
P75751
|
FINISHED |
| Object | ν |
—
|
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: ν | Statement: [Planck–Einstein relation, symbolForFrequency, ν]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolForFrequency Context triple: [Planck–Einstein relation, symbolForFrequency, ν]
-
A.
symbolForVelocity
Indicates that one entity is used as the symbolic representation or notation for the concept of velocity of another entity.
-
B.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
C.
hasFrequencyNote
Indicates that something is associated with a specific note describing how often it occurs or is repeated.
-
D.
symbolForConstant
Indicates that one entity serves as the symbolic representation or notation used to denote a particular constant.
-
E.
symbolForCharge
Indicates that one entity serves as the symbolic representation of the electric charge associated with another entity.
- 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea0d9b6c8190a0b5f0ab8d5cca19 |
completed | March 27, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6e8b5f6508190af28e06a7959d717 |
completed | March 27, 2026, 8:29 p.m. |
Created at: March 27, 2026, 2:54 p.m.