Triple
T22328725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kähler cone |
E551967
|
entity |
| Predicate | mayBeTrivialIf |
P102349
|
FINISHED |
| Object | manifold is non-Kähler |
—
|
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: manifold is non-Kähler | Statement: [Kähler cone, mayBeTrivialIf, manifold is non-Kähler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeTrivialIf Context triple: [Kähler cone, mayBeTrivialIf, manifold is non-Kähler]
-
A.
isTrivialWhen
chosen
Indicates that one condition, case, or problem becomes trivial or easily solvable when another specified condition holds.
-
B.
mayBeOmittedWhen
Indicates that one element is allowed to be left out or excluded under certain conditions defined by another element or context.
-
C.
canBeTruncated
Indicates that something is capable of being shortened or cut off, typically by removing a portion from its end.
-
D.
mayBeReplacedBy
Indicates that one entity can potentially be substituted or superseded by another entity.
-
E.
mayBeDeclared
Indicates that something has the potential or permission to be formally stated, specified, or announced, but has not necessarily been declared yet.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15769fdb48190b84e0c019ab63579 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.