Triple
T36017615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark II Telescope |
E1041888
|
entity |
| Predicate | supportsObservingBand |
P61515
|
FINISHED |
| Object | centimetre wavelengths |
—
|
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: centimetre wavelengths | Statement: [Mark II Telescope, supportsObservingBand, centimetre wavelengths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsObservingBand Context triple: [Mark II Telescope, supportsObservingBand, centimetre wavelengths]
-
A.
observesBand
Indicates that one entity watches, studies, or monitors a musical band.
-
B.
supportsObservation
Indicates that one entity provides evidence, context, or infrastructure that enables or strengthens the validity of an observation made about another entity.
-
C.
supportedBands
Indicates that one entity (typically a musician or band) performed as a supporting or opening act for another band.
-
D.
observingBand
Indicates that an entity is observing or monitoring another entity using a specific spectral band or frequency range.
-
E.
supportsSubbands
chosen
Indicates that one entity provides or is compatible with multiple subbands within a broader frequency or spectral band.
- 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.