Triple
T24810955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jones calculus |
E620785
|
entity |
| Predicate | typicalJonesMatrixSize |
P128192
|
FINISHED |
| Object | 2x2 complex matrix |
—
|
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: 2x2 complex matrix | Statement: [Jones calculus, typicalJonesMatrixSize, 2x2 complex matrix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalJonesMatrixSize Context triple: [Jones calculus, typicalJonesMatrixSize, 2x2 complex matrix]
-
A.
opticalSize
Indicates that one entity has a particular visual or perceived size relative to another, often dependent on viewing conditions or context.
-
B.
hasMatrixSize
chosen
Indicates that an entity (such as a matrix or array) has a specific dimensional size, typically expressed as its number of rows and columns.
-
C.
typicalDimension
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
D.
matrixSizeRule
Indicates a rule or constraint that specifies the required or allowed dimensions of a matrix in a given context.
-
E.
typicalPanelSize
Indicates the usual or standard dimensions associated with a given panel.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 18, 2026, 4:50 a.m.