Triple
T6877350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ampere |
E158703
|
entity |
| Predicate | isRelatedUnit |
P73892
|
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, isRelatedUnit, coulomb per second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRelatedUnit Context triple: [ampere, isRelatedUnit, coulomb per second]
-
A.
isUnitIn
Indicates that a specific unit is located within or belongs to a particular container, group, or context.
-
B.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
C.
isInternalUnitOf
Indicates that one unit functions as a subordinate or component part within the organizational structure of another unit.
-
D.
associatedWithUnit
Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
-
E.
isRelatedSymbol
Indicates that one symbol has a defined relationship or association with another symbol, such as similarity, correspondence, or functional connection.
- 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.