Triple

T33867775
Position Surface form Disambiguated ID Type / Status
Subject Joule E868103 entity
Predicate conversionToBTU P181791 FINISHED
Object 1 J ≈ 9.4782×10^-4 BTU 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 ≈ 9.4782×10^-4 BTU | Statement: [Joule, conversionToBTU, 1 J ≈ 9.4782×10^-4 BTU]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: conversionToBTU
Context triple: [Joule, conversionToBTU, 1 J ≈ 9.4782×10^-4 BTU]
  • A. conversionToKilowattHour
    Indicates the transformation of a quantity from its original energy or power unit into kilowatt-hours as the target unit of measurement.
  • B. relationToWatt
    Indicates a relationship that specifies how something is connected or related to Watt, such as by association, reference, or contextual linkage.
  • C. conversionToCalorie
    Indicates a relationship where a quantity is transformed or expressed in terms of its equivalent value in calories.
  • D. 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.
  • E. usesEnergyConversion
    Indicates that an entity performs or involves a process where one form of energy is transformed into another to achieve a function or outcome.
  • 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_69f7824dc3f0819092a5102895b4a478 completed May 3, 2026, 5:13 p.m.
PD Predicate disambiguation batch_69f780fc5ed88190b7200ee5a29940af completed May 3, 2026, 5:08 p.m.
PDg Predicate description generation batch_69f7817c79e081908e685c48165e086b completed May 3, 2026, 5:10 p.m.
Created at: May 1, 2026, 1:47 a.m.