Triple
T6877205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ampere |
E158700
|
entity |
| Predicate | hasNonSIUnitRelation |
P73885
|
FINISHED |
| Object | coulomb per second |
—
|
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: coulomb per second | Statement: [ampere, hasNonSIUnitRelation, coulomb per second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNonSIUnitRelation Context triple: [ampere, hasNonSIUnitRelation, coulomb per second]
-
A.
standardUnitRelation
Indicates a relationship where one unit is defined, measured, or interpreted in terms of a recognized standard unit.
-
B.
SIBaseUnitRelation
Indicates a relationship where one physical quantity or unit is defined, measured, or expressed in terms of one or more SI base units.
-
C.
hasSIUnitForConstant
Indicates that a given constant is associated with a specific SI (International System of Units) unit used to express its value.
-
D.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
-
E.
isCoherentSIUnit
Indicates that a unit is a valid, internally consistent unit within the International System of Units (SI), derived strictly from SI base units without additional numerical factors.
- 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_69c68832af1481908ce356e133ebaebe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8ccc29c8190904cb73c4cbb5dca |
completed | March 27, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b363dc8190a7225b540ab2bc40 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:22 p.m.