Triple
T3345129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwarzschild telescope |
E70354
|
entity |
| Predicate | hasImageSurface |
P47351
|
FINISHED |
| Object | curved focal surface |
—
|
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: curved focal surface | Statement: [Schwarzschild telescope, hasImageSurface, curved focal surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImageSurface Context triple: [Schwarzschild telescope, hasImageSurface, curved focal surface]
-
A.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
-
B.
hasKeyImage
Indicates that one entity is designated as the primary or representative image associated with another entity.
-
C.
hasHiddenImage
Indicates that an entity contains or is associated with an image that is not immediately visible or is intentionally concealed from normal view.
-
D.
hasMainImageSource
Indicates that an entity is associated with a primary image file or URL that serves as its main visual representation.
-
E.
supportsInterlacedCompositeArtifacts
Indicates that one entity provides compatibility with or functionality for handling interlaced composite artifacts associated with another entity.
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1f36c74819093ef2c74a46c2351 |
completed | March 8, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:12 p.m.