Triple

T23142524
Position Surface form Disambiguated ID Type / Status
Subject graph Laplacian E577498 entity
Predicate hasEigenvalue P128956 FINISHED
Object 0 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: 0 | Statement: [graph Laplacian, hasEigenvalue, 0]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEigenvalue
Context triple: [graph Laplacian, hasEigenvalue, 0]
  • A. hasEigenvalues chosen
    Indicates that a linear operator or matrix possesses one or more eigenvalues associated with its action on a vector space.
  • B. hasEffectiveEigenstate
    Indicates that an entity is associated with, or behaves as if it possesses, a particular eigenstate that effectively characterizes its observable properties or dynamics in a given context.
  • C. isEigenstateOf
    Indicates that a quantum state is an eigenstate of a given operator, meaning the operator acting on that state yields the same state scaled by a definite eigenvalue.
  • D. areEigenfunctionsOf
    Indicates that certain functions serve as eigenfunctions corresponding to a specified operator or transformation.
  • E. hasCPApproximateEigenvalue
    Indicates that one entity is an approximate eigenvalue of a completely positive (CP) map or operator associated with another entity.
  • 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_69e245f8e6248190ba3d58e068b4dccb completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18ecb72fc8190a24e8f5756217a36 completed April 29, 2026, 4:53 a.m.
PD Predicate disambiguation batch_69ef89f83b108190aaaa1db6221fc163 completed April 27, 2026, 4:08 p.m.
Created at: April 17, 2026, 4 p.m.