Triple
T33867773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joule |
E868103
|
entity |
| Predicate | conversionToCalorie |
P181471
|
FINISHED |
| Object | 1 J ≈ 0.239 cal |
—
|
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: 1 J ≈ 0.239 cal | Statement: [Joule, conversionToCalorie, 1 J ≈ 0.239 cal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionToCalorie Context triple: [Joule, conversionToCalorie, 1 J ≈ 0.239 cal]
-
A.
hasCalories
Indicates that an entity contains a specified amount of caloric energy.
-
B.
limitsMacronutrient
Indicates that one entity imposes a restriction or upper bound on the amount or proportion of a specific macronutrient associated with another entity.
-
C.
calorieLevel
Indicates the relationship between an entity and the amount of calories it contains or provides, typically categorized by intensity or range (e.g., low, medium, high).
-
D.
calorieProfile
Indicates the relationship between an entity and the detailed breakdown of its caloric characteristics, such as total calories and their distribution.
-
E.
conversionUse
Indicates that one entity is used as a means, method, or context for converting another entity from one form, state, or representation to another.
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69f77648979c8190b6cdbb835ab8987c |
completed | May 3, 2026, 4:22 p.m. |
Created at: May 1, 2026, 1:47 a.m.