Triple
T1840250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ekman transport |
E41160
|
entity |
| Predicate | governingEquation |
P12675
|
FINISHED |
| Object | M = τ / (ρ f) |
—
|
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: M = τ / (ρ f) | Statement: [Ekman transport, governingEquation, M = τ / (ρ f)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingEquation Context triple: [Ekman transport, governingEquation, M = τ / (ρ f)]
-
A.
mathematicallyExpressedBy
chosen
Indicates that something (such as a concept, quantity, or relationship) is represented or captured using a specific mathematical expression or formulation.
-
B.
mathematicallyFormulatedBy
Indicates that something (such as a concept, model, or theory) is expressed or defined using mathematical formulations created by a particular agent.
-
C.
formulaUsed
Indicates that a particular formula is employed or applied in performing a calculation, derivation, or reasoning step.
-
D.
governs
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
E.
isSolutionOf
Indicates that one entity is a correct answer or satisfies the conditions of a given problem, equation, or task.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafd88ebc81908208394746351fe6 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.