Triple
T10196832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infrared Spectrograph |
E238782
|
entity |
| Predicate | mayBeMountedOn |
P86781
|
FINISHED |
| Object | ground-based telescopes |
—
|
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: ground-based telescopes | Statement: [Infrared Spectrograph, mayBeMountedOn, ground-based telescopes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeMountedOn Context triple: [Infrared Spectrograph, mayBeMountedOn, ground-based telescopes]
-
A.
hasMount
Indicates that an entity is equipped with, riding, or otherwise using another entity as a mount for transportation or support.
-
B.
hasMountingFeature
Indicates that one entity includes or provides a structural feature intended for mounting or attaching another entity.
-
C.
mayBeHostedBy
chosen
Indicates that an entity has the possibility or option of being hosted or accommodated by another entity.
-
D.
mountingLocation
Indicates the physical position or surface on which something is attached, fixed, or installed.
-
E.
mountableBy
Indicates that one entity can be physically mounted, ridden, or climbed upon by another entity.
- 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_69ca84e1ea088190b38162e43d4cfa8f |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdedcaf6688190938d8e56e29493eb |
completed | April 2, 2026, 4:17 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:13 p.m.