Triple
T32308405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wirtinger derivatives |
E825427
|
entity |
| Predicate | assumeVariables |
P1458
|
FINISHED |
| Object | x and y real |
—
|
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: x and y real | Statement: [Wirtinger derivatives, assumeVariables, x and y real]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assumeVariables Context triple: [Wirtinger derivatives, assumeVariables, x and y real]
-
A.
usesVAR
Indicates that one entity makes use of, employs, or utilizes another entity as a variable or resource in performing some function or operation.
-
B.
coordinateVariables
Indicates that the variables are aligned or paired together in a shared coordinate system or structured correspondence.
-
C.
naturalVariables
Indicates that certain variables or parameters arise directly from the inherent properties or natural behavior of a system, rather than being externally imposed or artificially defined.
-
D.
assumes
chosen
Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
-
E.
involvesSubstitute
Indicates that one entity participates in a situation, event, or role as a replacement or stand-in for 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:45 a.m.