Triple
T23953775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamabe problem |
E603721
|
entity |
| Predicate | hasInvariantAssociated |
P29145
|
FINISHED |
| Object | Yamabe constant |
—
|
NE NERFINISHED |
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: Yamabe constant | Statement: [Yamabe problem, hasInvariantAssociated, Yamabe constant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInvariantAssociated Context triple: [Yamabe problem, hasInvariantAssociated, Yamabe constant]
-
A.
invariantOf
chosen
Indicates that one element is an invariant (a property or quantity that remains unchanged) with respect to another element, system, or transformation.
-
B.
invariantType
Indicates that one entity has a type or classification that remains constant or unchanged under specified conditions or transformations.
-
C.
hasIncidence
Indicates that a particular event, condition, or phenomenon occurs at a certain rate, frequency, or number of cases within a defined population or context.
-
D.
invariantSet
Indicates that a set remains unchanged under a specified transformation, operation, or dynamic process.
-
E.
hasAssociatedPhenomenon
Indicates that one entity is linked to, or typically occurs together with, a particular phenomenon or observable event.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d558748190a51b5732a3e6713c |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:21 p.m.