Triple
T15522150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XXZ spin chain |
E368993
|
entity |
| Predicate | hasRMatrix |
P114728
|
FINISHED |
| Object | trigonometric R-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: trigonometric R-matrix | Statement: [XXZ spin chain, hasRMatrix, trigonometric R-matrix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRMatrix Context triple: [XXZ spin chain, hasRMatrix, trigonometric R-matrix]
-
A.
hasMatrixType
chosen
Indicates that an entity is associated with or characterized by a specific type or category of matrix.
-
B.
hasMatrixOperations
Indicates that an entity supports or provides functionality for performing matrix-related operations.
-
C.
hasJacobian
Indicates that one entity is the Jacobian (derivative matrix) associated with another entity, typically describing how that entity changes with respect to its variables.
-
D.
hasDeterminant
Indicates that one entity functions as a determiner (e.g., article, demonstrative, quantifier) specifying or limiting the reference of another entity, typically a noun or noun phrase.
-
E.
hasAssociatedMatroid
Indicates that one object is linked to a specific matroid that is defined or associated with it.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0403543188190abac49d2b9decb89 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded28ab0588190a47a9090d1238707 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:04 a.m.