Triple
T25859346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPT collaboration |
E651438
|
entity |
| Predicate | usesTelescopeType |
P2518
|
FINISHED |
| Object | 10-meter millimeter/submillimeter-wavelength telescope |
—
|
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: 10-meter millimeter/submillimeter-wavelength telescope | Statement: [SPT collaboration, usesTelescopeType, 10-meter millimeter/submillimeter-wavelength telescope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTelescopeType Context triple: [SPT collaboration, usesTelescopeType, 10-meter millimeter/submillimeter-wavelength telescope]
-
A.
hasSurveyTelescope
Indicates that an entity possesses or is equipped with a survey telescope used for wide-area observational surveys.
-
B.
telescopeType
chosen
Indicates the specific kind or category of telescope associated with an entity.
-
C.
usedOnTelescope
Indicates that something is employed or applied in the operation or functioning of a telescope.
-
D.
seeType
Indicates that one entity observes, recognizes, or visually perceives another entity of a particular type or category.
-
E.
hasTelescopeNamedAfterHer
Indicates that a telescope is named in honor of the referenced female individual.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6026a80208190a8b1fae20d6ed906 |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 8:04 a.m.