Triple
T7188650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coulomb |
E167631
|
entity |
| Predicate | dimensionOfTemperature |
P75641
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [coulomb, dimensionOfTemperature, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dimensionOfTemperature Context triple: [coulomb, dimensionOfTemperature, 0]
-
A.
typicalTemperatureScale
Indicates the temperature scale (such as Celsius or Fahrenheit) that is normally used to express temperature values for the given entity or context.
-
B.
dimensionOfEnergy
Indicates a relationship where a specified dimension or unit is associated with a particular measure or quantity of energy.
-
C.
natureOfUnit
Indicates the type or category that characterizes what kind of unit something is (e.g., its nature or classification as a unit).
-
D.
temperatureOrderOfMagnitude
Indicates that the temperatures of the related entities differ by approximately a specified order of magnitude (i.e., by a power-of-ten scale factor).
-
E.
symbolOfTemperature
Indicates that one entity serves as a symbolic representation or notation used to express the temperature of another entity.
- F. None of above. chosen
Provenance (4 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e8e3d9188190ba2792098d76fb86 |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e8b5f6508190af28e06a7959d717 |
completed | March 27, 2026, 8:29 p.m. |
Created at: March 27, 2026, 2:50 p.m.