Triple
T26564383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | henry (unit) |
E666335
|
entity |
| Predicate | baseUnitAmpereExponent |
P56838
|
FINISHED |
| Object | -2 |
—
|
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: -2 | Statement: [henry (unit), baseUnitAmpereExponent, -2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseUnitAmpereExponent Context triple: [henry (unit), baseUnitAmpereExponent, -2]
-
A.
baseUnitMetreExponent
Indicates the exponent to which the base unit metre is raised in expressing a compound or derived measurement.
-
B.
baseUnitsLengthExponent
Indicates the exponent applied to the base unit of length in a compound or derived measurement expression.
-
C.
baseUnitsCurrentExponent
chosen
Indicates the exponent to which the base unit of electric current is raised in the dimensional representation of a physical quantity.
-
D.
baseUnitsMassExponent
Indicates the exponent applied to the base unit of mass in a measurement’s dimensional or unit expression.
-
E.
baseUnitsTimeExponent
Indicates the exponent applied to the time dimension in the base units that define a derived physical quantity.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6149cc0c88190aadaacfa45a2382e |
completed | May 2, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:54 a.m.