Triple
T1535884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ampère–Maxwell law |
E32547
|
entity |
| Predicate | containsConstant |
P9782
|
FINISHED |
| Object | vacuum permeability μ₀ |
—
|
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: vacuum permeability μ₀ | Statement: [Ampère–Maxwell law, containsConstant, vacuum permeability μ₀]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsConstant Context triple: [Ampère–Maxwell law, containsConstant, vacuum permeability μ₀]
-
A.
includesConstant
chosen
Indicates that one entity contains or explicitly references a specific constant value within its definition or structure.
-
B.
usesConstant
Indicates that one entity makes use of a specific constant value defined or provided by another entity.
-
C.
containsDeclaration
Indicates that one entity includes or holds within it a formal declaration associated with another entity.
-
D.
relatedConstant
Indicates that one entity is a fixed, unchanging value or constant that is associated with or linked to another entity.
-
E.
constant
Indicates that the relationship or value does not change across different instances, contexts, or over time.
- 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_69a885ea86308190998f6bc14bb91f8e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a915f323bc8190aa757142c225e0ae |
completed | March 5, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69a907b046448190be8ea4d7b20255f7 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.