Triple
T4659224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kronecker product |
E102485
|
entity |
| Predicate | linearity |
P58258
|
FINISHED |
| Object | bilinear in both arguments |
—
|
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: bilinear in both arguments | Statement: [Kronecker product, linearity, bilinear in both arguments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linearity Context triple: [Kronecker product, linearity, bilinear in both arguments]
-
A.
isLinear
Indicates that a relationship, function, or structure preserves linearity, typically meaning it satisfies additivity and homogeneity (or forms a straight-line dependence between variables).
-
B.
usesLineCharacteristic
Indicates that one entity employs or is based on a specific characteristic or property of a line.
-
C.
slopeUse
Indicates how a particular slope or gradient is utilized or purposed in relation to another entity.
-
D.
criticalLine
Indicates that one entity is a crucial or decisive line (such as a boundary, path, or threshold) whose state or position significantly affects the other entity or overall system.
-
E.
lineType
Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
- 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6328387c81909a500e694a739e6e |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:15 p.m.