Triple
T36467715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marchenko–Pastur law |
E898463
|
entity |
| Predicate | noAtomAtZero |
P185534
|
FINISHED |
| Object | when λ ≥ 1 |
—
|
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: when λ ≥ 1 | Statement: [Marchenko–Pastur law, noAtomAtZero, when λ ≥ 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: noAtomAtZero Context triple: [Marchenko–Pastur law, noAtomAtZero, when λ ≥ 1]
-
A.
isZeroFor
Indicates that a given value, expression, or function evaluates to zero when applied to or considered with respect to a specified entity or context.
-
B.
hasZeroPosition
Indicates that an entity occupies or is assigned to the reference (zero) position within a defined coordinate system or ordered structure.
-
C.
zeroDefinition
Indicates that something has no defined value, quantity, or specification within the given context.
-
D.
zeroSymmetry
Indicates that the relationship or structure remains unchanged when the zero element is applied or considered, reflecting invariance under the presence of zero.
-
E.
zeroMassCase
Indicates a situation or scenario in which the mass of the relevant object or system is assumed or defined to be zero.
- F. None of above. chosen
Provenance (4 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.