Triple
T4597302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kronecker delta |
E100234
|
entity |
| Predicate | usedToExpress |
P51567
|
FINISHED |
| Object | orthonormality of basis vectors |
—
|
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: orthonormality of basis vectors | Statement: [Kronecker delta, usedToExpress, orthonormality of basis vectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToExpress Context triple: [Kronecker delta, usedToExpress, orthonormality of basis vectors]
-
A.
usedToExplain
Indicates that one entity serves as an explanation or clarification for another entity.
-
B.
expresses
Indicates that one entity conveys, communicates, or articulates a thought, feeling, or idea through another medium or form.
-
C.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
usedInExpression
chosen
Indicates that one entity (typically a term, symbol, or construct) is employed as a component within another entity that represents an expression.
-
E.
usedInSpokenForm
Indicates that something (such as a word, name, or expression) is employed in spoken language or oral communication.
- 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_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. |
Created at: March 20, 2026, 1:11 p.m.