Triple
T11317095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arecibo L-band Feed Array survey |
E267994
|
entity |
| Predicate | usesWavelengthBand |
P90456
|
FINISHED |
| Object | L-band |
—
|
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: L-band | Statement: [Arecibo L-band Feed Array survey, usesWavelengthBand, L-band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesWavelengthBand Context triple: [Arecibo L-band Feed Array survey, usesWavelengthBand, L-band]
-
A.
usedWavelengthRange
chosen
Indicates the range of wavelengths that were employed or applied in performing a particular process, measurement, or operation.
-
B.
supportsWavelengthRange
Indicates that an entity is capable of operating over, handling, or being compatible with a specified range of wavelengths.
-
C.
wavelengthDependence
Indicates that one quantity or effect varies as a function of the wavelength of radiation or a wave.
-
D.
hasObservationWavelength
Indicates the specific wavelength at which an observation or measurement is made or recorded.
-
E.
channelWavelength
Indicates the specific wavelength at which a given channel operates or is defined.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c3cf748190987838029d9f7fff |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.