Triple
T4667901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heaviside step function |
E102892
|
entity |
| Predicate | alternativeConvention |
P47902
|
FINISHED |
| Object | H(0)=0 |
—
|
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: H(0)=0 | Statement: [Heaviside step function, alternativeConvention, H(0)=0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeConvention Context triple: [Heaviside step function, alternativeConvention, H(0)=0]
-
A.
associatedConvention
Indicates a relationship where something is linked or connected to a particular convention (such as an event, standard, or formal gathering).
-
B.
logicConvention
Indicates a relationship where entities participate in or are associated with a convention, event, or standard related to logic or logical systems.
-
C.
alternativeForm
Indicates that one entity is an alternative version, variant, or representation of another entity.
-
D.
isArbitraryConvention
chosen
Indicates that the relationship or rule exists due to social or contextual agreement rather than inherent necessity or natural law.
-
E.
alternateMode
Indicates that one entity functions as an alternative form, configuration, or mode of operation 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_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.