Triple
T1348232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck constant |
E28819
|
entity |
| Predicate | definesRelation |
P8534
|
FINISHED |
| Object | E = h ν |
—
|
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: E = h ν | Statement: [Planck constant, definesRelation, E = h ν]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesRelation Context triple: [Planck constant, definesRelation, E = h ν]
-
A.
definesRelationshipBetween
chosen
Indicates that one entity specifies or establishes the nature, type, or rules of a relationship that exists between two or more other entities.
-
B.
datumRelation
Indicates a relationship where one piece of data is connected to, derived from, or otherwise associated with another piece of data.
-
C.
supportsRelation
Indicates that one entity provides assistance, endorsement, or structural backing to another entity or its activity.
-
D.
semanticRelation
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
-
E.
DSTRelation
Indicates a temporal relationship where one event, state, or timestamp is adjusted or interpreted according to Daylight Saving Time rules.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c2418e38819094683d6e1efc6e56 |
completed | March 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.