Triple
T6482376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | newton |
E146424
|
entity |
| Predicate | inImperialSystemApprox |
P71161
|
FINISHED |
| Object | 0.225 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: 0.225 lbf | Statement: [newton, inImperialSystemApprox, 0.225 lbf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inImperialSystemApprox Context triple: [newton, inImperialSystemApprox, 0.225 lbf]
-
A.
isMetric
Indicates that something satisfies the properties required to be considered a metric, such as defining distances that obey non-negativity, identity, symmetry, and the triangle inequality.
-
B.
usesMeasurementSystem
Indicates that one entity adopts or applies a particular system of measurement defined by another entity.
-
C.
unitUK
Indicates that one entity uses or is measured in a unit of measure that is specific to or standard within the United Kingdom.
-
D.
usesMetric
Indicates that one entity adopts, applies, or relies on a particular metric or measurement standard in its operation, evaluation, or description.
-
E.
meterSystem
Indicates that one entity uses, is measured in, or is associated with a particular system of meters or measurement units.
- 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_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. |
| PDg | Predicate description generation | batch_69c06822f73081908e6bb9edecbe77a6 |
completed | March 22, 2026, 10:07 p.m. |
Created at: March 22, 2026, 4:51 p.m.