Triple
T65793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwarzschild black hole |
E1310
|
entity |
| Predicate | hasPhotonSphere |
P4456
|
FINISHED |
| Object | radius 3GM/c^2 |
—
|
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: radius 3GM/c^2 | Statement: [Schwarzschild black hole, hasPhotonSphere, radius 3GM/c^2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhotonSphere Context triple: [Schwarzschild black hole, hasPhotonSphere, radius 3GM/c^2]
-
A.
hasLighting
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
B.
hasPolarRadius
Indicates that an entity possesses a specific radius measured from its center to its pole, typically used for spheroidal or planetary bodies.
-
C.
hasMagnetosphere
Indicates that an astronomical body possesses a magnetic field strong enough to create a surrounding magnetosphere.
-
D.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
E.
hasFieldOfView
Indicates that one entity possesses a visual coverage area within which it can perceive or detect other entities or regions.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a2516eda54819090f5c14384d4eab1 |
completed | Feb. 28, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69a24ea5c140819080409a968c8d2ce8 |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a2516d98e88190b79261bd3fcadd9b |
completed | Feb. 28, 2026, 2:22 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.