Triple
T1250517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawking radiation |
E26863
|
entity |
| Predicate | emissionRegion |
P8054
|
FINISHED |
| Object | near the event horizon |
—
|
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: near the event horizon | Statement: [Hawking radiation, emissionRegion, near the event horizon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emissionRegion Context triple: [Hawking radiation, emissionRegion, near the event horizon]
-
A.
observedInRegion
chosen
Indicates that something has been detected, recorded, or seen occurring within a specified geographic or spatial region.
-
B.
emergedInRegion
Indicates that something first appeared, originated, or came into existence within a specified geographic region.
-
C.
spectralRegion
Indicates the portion of the electromagnetic spectrum (e.g., wavelength or frequency range) in which a measurement, observation, or property is defined or applies.
-
D.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
-
E.
regionExposure
Indicates that an entity is subject to or affected by exposure within a specific geographic or spatial region.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf84c73c8190bbb14265cd7ab6ae |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6b075881908e867c25b5080e25 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.