Triple
T12070579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weyl tensor |
E287410
|
entity |
| Predicate | canBeNonzeroIn |
P9151
|
FINISHED |
| Object | vacuum regions of spacetime |
—
|
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: vacuum regions of spacetime | Statement: [Weyl tensor, canBeNonzeroIn, vacuum regions of spacetime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeNonzeroIn Context triple: [Weyl tensor, canBeNonzeroIn, vacuum regions of spacetime]
-
A.
isNonzeroFor
chosen
Indicates that a given value, function, or quantity is not equal to zero under specified conditions or for specified inputs.
-
B.
isNonZeroBecause
Indicates that a value is non-zero specifically due to the stated cause, reason, or contributing factor.
-
C.
isNonNegative
Indicates that a value is greater than or equal to zero.
-
D.
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.
-
E.
canBeDefinedFor
Indicates that a certain concept, operation, or property is applicable to and can be meaningfully specified for a given entity or set of entities.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bda47c8190b94860b31df4a98c |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:48 p.m.