Triple
T33829911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M30 |
E867066
|
entity |
| Predicate | resolvableInTelescope |
P61266
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [M30, resolvableInTelescope, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resolvableInTelescope Context triple: [M30, resolvableInTelescope, yes]
-
A.
requiresTelescopeAperture
Indicates that performing the specified observation or task depends on using a telescope with at least a certain aperture size.
-
B.
usedOnTelescope
Indicates that something is employed or applied in the operation or functioning of a telescope.
-
C.
isResolvedIntoIndividualStars
chosen
Indicates that an object or region, previously appearing as a single source, can be distinguished into its constituent individual stars.
-
D.
hasAuxiliaryTelescopes
Indicates that an entity is equipped with or includes additional telescopes that serve as auxiliary instruments to a primary telescope system.
-
E.
canBeSeenFromEarthWith
Indicates that one entity is visible from Earth using the specified instrument, method, or observational aid.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70022ccc88190abdc55e89e3d3172 |
completed | May 3, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.