Triple
T6482390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | newton |
E146424
|
entity |
| Predicate | relationToJoule |
P11666
|
FINISHED |
| Object | 1 J = 1 N·m |
—
|
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 = 1 N·m | Statement: [newton, relationToJoule, 1 J = 1 N·m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToJoule Context triple: [newton, relationToJoule, 1 J = 1 N·m]
-
A.
dimensionOfEnergy
Indicates a relationship where a specified dimension or unit is associated with a particular measure or quantity of energy.
-
B.
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.
-
C.
energyContribution
Indicates the amount or role of energy that one entity provides or contributes to another entity, process, or system.
-
D.
energyPerDegreeOfFreedom
Indicates the amount of energy associated with each independent degree of freedom in a physical system.
-
E.
standardUnitRelation
chosen
Indicates a relationship where one unit is defined, measured, or interpreted in terms of a recognized standard 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_69c0090158c08190af0df9a2348d2d52 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a6b2e9881908b715573e7ba7458 |
completed | March 22, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:51 p.m.