Triple
T6877172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ampère's force law |
E158699
|
entity |
| Predicate | conceptualBasisFor |
P64521
|
FINISHED |
| Object | electromagnetic unit of current |
—
|
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: electromagnetic unit of current | Statement: [Ampère's force law, conceptualBasisFor, electromagnetic unit of current]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conceptualBasisFor Context triple: [Ampère's force law, conceptualBasisFor, electromagnetic unit of current]
-
A.
basingConcept
chosen
Indicates that one concept serves as the foundational basis or underlying rationale for another concept.
-
B.
isConceptual
Indicates that something exists as an abstract or theoretical idea rather than as a concrete, physical entity.
-
C.
hasConcept
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
D.
becameBasisOf
Indicates that one entity served as the foundational source, model, or starting point upon which another entity was developed, derived, or established.
-
E.
hasConceptualOrigin
Indicates that something conceptually originates from, is derived from, or is fundamentally based on another thing.
- 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_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. |
Created at: March 27, 2026, 2:22 p.m.