Triple
T461824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Sitter spacetime |
E7354
|
entity |
| Predicate | hasLimitCase |
P9149
|
FINISHED |
| Object | Minkowski spacetime for Λ → 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: Minkowski spacetime for Λ → 0 | Statement: [de Sitter spacetime, hasLimitCase, Minkowski spacetime for Λ → 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLimitCase Context triple: [de Sitter spacetime, hasLimitCase, Minkowski spacetime for Λ → 0]
-
A.
isLimitOf
chosen
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
B.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
C.
hasCase
Indicates that one entity is involved in, associated with, or characterized by a particular case, instance, or occurrence represented by another entity.
-
D.
hasNumberOfCasesApprox
Indicates that an entity is associated with an approximate (not exact) count of cases.
-
E.
hasSpeedLimit
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efbed5b88190a45716812eb4cfdf |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2ede8eac081908dffade6a5e7950b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.