Triple
T33867816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joule’s law of heating |
E868104
|
entity |
| Predicate | unitOfHeatEnergy |
P12631
|
FINISHED |
| Object | joule |
—
|
NE NERFINISHED |
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: joule | Statement: [Joule’s law of heating, unitOfHeatEnergy, joule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitOfHeatEnergy Context triple: [Joule’s law of heating, unitOfHeatEnergy, joule]
-
A.
hasOrderOfMagnitudeInJoules
Indicates that the quantity associated with an entity is approximately of a specified order of magnitude when measured in joules.
-
B.
unitOfMeasure
chosen
Indicates that one entity specifies the standard unit in which the quantity or value of another entity is measured.
-
C.
hasCommonEnergyUnitForm
Indicates that two energy quantities share the same unit representation or can be expressed in an equivalent standardized energy unit form.
-
D.
dimensionOfTemperature
Indicates that one entity represents the physical dimension or measure associated with temperature for another entity.
-
E.
natureOfUnit
Indicates the type or category that characterizes what kind of unit something is (e.g., its nature or classification as a unit).
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f700a4c7148190b03b64c27289043d |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5a4f7881909324eb3c20ca96f1 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.