Triple
T33867776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joule |
E868103
|
entity |
| Predicate | conversionToFootPound |
P182282
|
FINISHED |
| Object | 1 J ≈ 0.737562 ft·lbf |
—
|
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.737562 ft·lbf | Statement: [Joule, conversionToFootPound, 1 J ≈ 0.737562 ft·lbf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionToFootPound Context triple: [Joule, conversionToFootPound, 1 J ≈ 0.737562 ft·lbf]
-
A.
conversionToBTU
Indicates a relationship where a quantity is converted into its equivalent value measured in British Thermal Units (BTU).
-
B.
conversionToCalorie
Indicates a relationship where a quantity is transformed or expressed in terms of its equivalent value in calories.
-
C.
conversionToKilowattHour
Indicates the transformation of a quantity from its original energy or power unit into kilowatt-hours as the target unit of measurement.
-
D.
relationToWatt
Indicates a relationship that specifies how something is connected or related to Watt, such as by association, reference, or contextual linkage.
-
E.
conversionToWeber
Indicates a relationship where a quantity is converted into an equivalent value expressed in webers, the SI unit of magnetic flux.
- 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_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: May 1, 2026, 1:47 a.m.