Triple
T7489924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | t_P |
E176978
|
entity |
| Predicate | isDefinedInTermsOf |
P27208
|
FINISHED |
| Object | ħ = h / (2π) |
—
|
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: ħ = h / (2π) | Statement: [t_P, isDefinedInTermsOf, ħ = h / (2π)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDefinedInTermsOf Context triple: [t_P, isDefinedInTermsOf, ħ = h / (2π)]
-
A.
areDefinedIn
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
B.
isCommonlyDefinedBy
Indicates that something is typically or most frequently characterized, specified, or described by a particular definition, property, or set of criteria.
-
C.
hasSemanticsDefinedBy
Indicates that the meaning or interpretation of one entity is specified, constrained, or determined by another entity.
-
D.
definedInField
Indicates that something (such as a concept, method, or element) is formally specified, declared, or established within a particular field, domain, or area of study.
-
E.
definedVia
chosen
Indicates that one entity is specified, characterized, or given its meaning by reference to another entity or construct.
- 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f55bdb3481908653b46eafba011d |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:43 p.m.