Triple
T1463182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faraday's law of induction |
E31559
|
entity |
| Predicate | integralForm |
P12675
|
FINISHED |
| Object | ∮_C E · dl = - dΦ_B/dt |
—
|
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: ∮_C E · dl = - dΦ_B/dt | Statement: [Faraday's law of induction, integralForm, ∮_C E · dl = - dΦ_B/dt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integralForm Context triple: [Faraday's law of induction, integralForm, ∮_C E · dl = - dΦ_B/dt]
-
A.
integrates
Indicates that one entity combines or brings together another entity or set of entities into a unified, functioning whole.
-
B.
generalizedForm
Indicates that one entity is a more abstract, generalized version or broader form of another entity.
-
C.
mathematicallyExpressedBy
chosen
Indicates that something (such as a concept, quantity, or relationship) is represented or captured using a specific mathematical expression or formulation.
-
D.
alternativeForm
Indicates that one entity is an alternative version, variant, or representation of another entity.
-
E.
logicalForm
Indicates a relationship where an expression is associated with its structured, formal logical representation.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5b89708819084fb9ba4ff293b8b |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48121e48190946c23c583e5fb64 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.