Triple
T9937755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayward black hole model |
E193998
|
entity |
| Predicate | hasInteriorBehavior |
P91244
|
FINISHED |
| Object | de Sitter-like at small radius |
—
|
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: de Sitter-like at small radius | Statement: [Hayward black hole model, hasInteriorBehavior, de Sitter-like at small radius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteriorBehavior Context triple: [Hayward black hole model, hasInteriorBehavior, de Sitter-like at small radius]
-
A.
hasInteriorFeature
Indicates that an entity contains or includes a specific feature within its interior space.
-
B.
hasInteriorPeriod
Indicates that an entity includes or is associated with a specific time interval occurring within its overall duration.
-
C.
hasInteriorColor
Indicates that an entity possesses a specific color used on its interior surfaces or internal parts.
-
D.
hasEmptyInterior
Indicates that the interior of an entity is completely hollow or contains no material.
-
E.
hasCoreBehavior
Indicates that an entity possesses or exhibits a fundamental, defining behavior that is central to its function or identity.
- F. None of above. chosen
Provenance (4 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5e64760819094f599f158d32f33 |
completed | April 2, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:44 p.m.