Triple
T10739228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydrodynamics |
E253276
|
entity |
| Predicate | mathematicalLevel |
P95728
|
FINISHED |
| Object | advanced calculus |
—
|
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: advanced calculus | Statement: [Hydrodynamics, mathematicalLevel, advanced calculus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mathematicalLevel Context triple: [Hydrodynamics, mathematicalLevel, advanced calculus]
-
A.
mathematicalSchool
Indicates a relationship where an entity is associated with, belongs to, or is characterized by a particular school or tradition within mathematics.
-
B.
mathematicallyUses
Indicates that one entity employs or applies another entity within a mathematical context, such as in a formula, proof, computation, or theoretical framework.
-
C.
supportsMathematicsTopic
Indicates that one entity provides assistance, resources, or reinforcement for understanding or working with a particular mathematics topic.
-
D.
trainingLevel
Indicates the degree or stage of training or skill development that an entity has attained.
-
E.
assessmentLevel
Indicates the degree, rating, or intensity assigned to an evaluation or judgment of something.
- F. None of above. chosen
Provenance (4 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d710424d8c81908ee9b59d622f2af5 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa323564819097b207eb53f8a9b8 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:14 p.m.