Triple
T1348238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck constant |
E28819
|
entity |
| Predicate | isExactByDefinition |
P9774
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Planck constant, isExactByDefinition, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExactByDefinition Context triple: [Planck constant, isExactByDefinition, true]
-
A.
hasExactValue
chosen
Indicates that an entity possesses a specific, precisely defined value that must match exactly, without any deviation or tolerance.
-
B.
areDefinedIn
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
C.
isDistinguishedBy
Indicates that one entity is characterized or set apart from others by a particular feature, quality, or attribute.
-
D.
equivalentTo
Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given context.
-
E.
isDistinctFrom
Indicates that two entities are not identical and can be clearly distinguished from one another.
- 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.