Triple
T6832956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | linear algebra |
E157381
|
entity |
| Predicate | hasKeyOperation |
P1137
|
FINISHED |
| Object | matrix multiplication |
—
|
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: matrix multiplication | Statement: [linear algebra, hasKeyOperation, matrix multiplication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyOperation Context triple: [linear algebra, hasKeyOperation, matrix multiplication]
-
A.
hasKeyAction
Indicates that an entity performs or is associated with a primary or essential action within a given context.
-
B.
hasOperationType
chosen
Indicates the specific kind or category of operation associated with an entity or process.
-
C.
hasKeyFunction
Indicates that one entity serves as a primary or essential function or role for another entity.
-
D.
hasKeyState
Indicates that an entity possesses or is associated with a particular key-related status or condition (such as pressed, released, enabled, or disabled).
-
E.
hasKeyElement
Indicates that one entity contains or depends on another entity that serves as a primary or essential component.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d62b1e8c8190a81d91191a54b073 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.