Triple
T24811007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mueller calculus |
E620786
|
entity |
| Predicate | dimensionOfMuellerMatrix |
P12688
|
FINISHED |
| Object | 4x4 |
—
|
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: 4x4 | Statement: [Mueller calculus, dimensionOfMuellerMatrix, 4x4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dimensionOfMuellerMatrix Context triple: [Mueller calculus, dimensionOfMuellerMatrix, 4x4]
-
A.
dimensionCount
Indicates the number of distinct dimensions or axes associated with an entity or data structure.
-
B.
dimensionOfComponents
chosen
Indicates that a specified dimension value is associated with, or applies to, the components of an object or system.
-
C.
numberOfIndependentMatrices
Indicates the count of matrices in a set that are linearly independent from each other.
-
D.
dimensionVector
Indicates a vector that specifies the magnitudes or extents of an entity along multiple dimensions or measurement axes.
-
E.
dimensionFormula
Indicates a mathematical or logical expression that defines how a particular dimension (such as size, measure, or extent) is derived or calculated from other quantities.
- 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_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:50 a.m.