Triple
T23837514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rindler wedge |
E590892
|
entity |
| Predicate | causalBoundary |
P25792
|
FINISHED |
| Object | Rindler horizon formed by null surfaces |
—
|
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: Rindler horizon formed by null surfaces | Statement: [Rindler wedge, causalBoundary, Rindler horizon formed by null surfaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causalBoundary Context triple: [Rindler wedge, causalBoundary, Rindler horizon formed by null surfaces]
-
A.
hasConceptualBoundary
Indicates that one entity defines, marks, or establishes the abstract limit or scope of another entity’s meaning, applicability, or conceptual extent.
-
B.
crossedBoundary
Indicates that an entity has moved from one defined area, region, or limit into another, thereby passing across a specified boundary.
-
C.
boundaryCase
Indicates that one entity represents a limiting or extreme condition used to test or define the valid range or behavior of another entity.
-
D.
hasBoundaryInfluenceFrom
Indicates that the boundary or limits of one entity are affected, shaped, or determined by another entity.
-
E.
boundaryCondition
chosen
Indicates the specific constraints or values imposed at the limits or edges of a system, domain, or process that govern its behavior there.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c883c7108190b3cce6fec0b8609a |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:07 p.m.