Triple
T1249078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snell’s law of refraction |
E26832
|
entity |
| Predicate | equationForm |
P12675
|
FINISHED |
| Object | n1 * sin(θ1) = n2 * sin(θ2) |
—
|
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: n1 * sin(θ1) = n2 * sin(θ2) | Statement: [Snell’s law of refraction, equationForm, n1 * sin(θ1) = n2 * sin(θ2)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equationForm Context triple: [Snell’s law of refraction, equationForm, n1 * sin(θ1) = n2 * sin(θ2)]
-
A.
formsFrom
Indicates that one entity is created, derived, or takes shape as a result of another entity.
-
B.
mathematicallyExpressedBy
chosen
Indicates that something (such as a concept, quantity, or relationship) is represented or captured using a specific mathematical expression or formulation.
-
C.
formulaUsed
Indicates that a particular formula is employed or applied in performing a calculation, derivation, or reasoning step.
-
D.
logicalForm
Indicates a relationship where an expression is associated with its structured, formal logical representation.
-
E.
alternativeForm
Indicates that one entity is an alternative version, variant, or representation of another entity.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf83b32c81908648e5748b897247 |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6b075881908e867c25b5080e25 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.