Triple
T4597274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kronecker delta |
E100234
|
entity |
| Predicate | hasAlternativeNotation |
P57346
|
FINISHED |
| Object | δ(i,j) |
—
|
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: δ(i,j) | Statement: [Kronecker delta, hasAlternativeNotation, δ(i,j)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeNotation Context triple: [Kronecker delta, hasAlternativeNotation, δ(i,j)]
-
A.
hasAlternativeVocalization
Indicates that an entity has another valid way it can be vocalized or pronounced, distinct from its primary or standard vocalization.
-
B.
distinguishingNotation
Indicates that one entity uses a specific notation or symbol to distinguish or differentiate another entity from similar ones.
-
C.
isAlternativeTo
Indicates that one entity can serve as a substitute or different option in place of another.
-
D.
typicalNotation
Indicates that one entity is the standard or commonly used symbolic representation (notation) for another entity.
-
E.
usesSubtractiveNotation
Indicates that something represents values by subtracting one symbol’s value from another, as in numeral systems where smaller units placed before larger ones denote a difference rather than a sum.
- 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59420c108190b5c2c5039e964da5 |
completed | March 20, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56b5f4648190834eafa666d53caa |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:11 p.m.