Triple
T1462809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wien displacement law |
E31550
|
entity |
| Predicate | hasEquation |
P12675
|
FINISHED |
| Object | λ_max = b / T |
—
|
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: λ_max = b / T | Statement: [Wien displacement law, hasEquation, λ_max = b / T]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEquation Context triple: [Wien displacement law, hasEquation, λ_max = b / T]
-
A.
hasEquivalent
Indicates that two entities are considered equal in value, meaning, or function within a given context.
-
B.
numberOfIndependentEquations
Indicates the count of distinct, non-redundant equations that independently constrain or relate the variables in a system.
-
C.
isSolutionOf
Indicates that one entity is a correct answer or satisfies the conditions of a given problem, equation, or task.
-
D.
admitsSolution
Indicates that a problem, system, or situation allows for or possesses at least one valid solution.
-
E.
mathematicallyExpressedBy
chosen
Indicates that something (such as a concept, quantity, or relationship) is represented or captured using a specific mathematical expression or formulation.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5b6e36c81909c47b2f7e66f17d7 |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48121e48190946c23c583e5fb64 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.