Triple
T7188642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coulomb |
E167631
|
entity |
| Predicate | SIBaseRelation |
P58687
|
FINISHED |
| Object | 1 C = 1 A × 1 s |
—
|
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 C = 1 A × 1 s | Statement: [coulomb, SIBaseRelation, 1 C = 1 A × 1 s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SIBaseRelation Context triple: [coulomb, SIBaseRelation, 1 C = 1 A × 1 s]
-
A.
SIBaseUnitRelation
chosen
Indicates a relationship where one physical quantity or unit is defined, measured, or expressed in terms of one or more SI base units.
-
B.
stepRelation
Indicates a relationship where one entity is a step-relative of another, such as a stepparent, stepchild, or stepsibling connection.
-
C.
datumRelation
Indicates a relationship where one piece of data is connected to, derived from, or otherwise associated with another piece of data.
-
D.
DSTRelation
Indicates a temporal relationship where one event, state, or timestamp is adjusted or interpreted according to Daylight Saving Time rules.
-
E.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e8e3d9188190ba2792098d76fb86 |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:50 p.m.