Triple
T4667930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heaviside step function |
E102892
|
entity |
| Predicate | shiftParameter |
P12016
|
FINISHED |
| Object | a is the step location |
—
|
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: a is the step location | Statement: [Heaviside step function, shiftParameter, a is the step location]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shiftParameter Context triple: [Heaviside step function, shiftParameter, a is the step location]
-
A.
parameter
chosen
Indicates that one entity serves as a parameter or argument that configures, constrains, or influences the behavior or outcome of another entity or process.
-
B.
marksShiftToward
Indicates a change or transition from one state, condition, or position toward another, highlighting the direction or trend of that shift.
-
C.
shiftedUnder
Indicates that one entity has been moved or displaced to a position beneath another entity.
-
D.
policyShift
Indicates a change or adjustment in an existing policy, typically reflecting a new direction, priority, or approach.
-
E.
positionChange
Indicates a change in an entity’s spatial or positional state from one location or configuration to another.
- 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.