Triple
T31943657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V_us |
E815589
|
entity |
| Predicate | relatedByUnitarityTo |
—
|
GENERATED |
| Object | V_ud |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedByUnitarityTo Context triple: [V_us, relatedByUnitarityTo, V_ud]
-
A.
satisfiesUnitarityRelationWith
chosen
Indicates that one entity and another are related in such a way that together they fulfill a required unitarity condition or constraint.
-
B.
isRelatedUnit
Indicates that one unit has a defined relationship or association with another unit within a given system or context.
-
C.
isUnitary
Indicates that an entity (such as an operator, matrix, or transformation) preserves inner products and norms, typically meaning its inverse equals its adjoint (or conjugate transpose).
-
D.
associatedWithUnit
Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
-
E.
relatedByFormula
Indicates that one entity is mathematically or logically derived from, or connected to, another according to a specific formula.
- F. None of above.
Provenance (1 batch)
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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:06 a.m.