Triple
T6938915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stefan–Boltzmann constant |
E160622
|
entity |
| Predicate | isExact |
P62237
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Stefan–Boltzmann constant, isExact, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExact Context triple: [Stefan–Boltzmann constant, isExact, false]
-
A.
isExactSince
Indicates that a condition, state, or relationship has held precisely from a specific starting time onward, with that start time being exact rather than approximate.
-
B.
hasExactValue
Indicates that an entity possesses a specific, precisely defined value that must match exactly, without any deviation or tolerance.
-
C.
constantExactness
chosen
Indicates that a value or relationship holds with complete, unvarying precision, without any approximation or deviation.
-
D.
exactFor
Indicates that one entity corresponds to or matches another entity with complete precision, without any deviation or approximation.
-
E.
isExplicit
Indicates that something is stated clearly and directly, leaving no room for ambiguity or implied interpretation.
- 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:28 p.m.