Triple
T7272484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Very Long Baseline Array |
E161138
|
entity |
| Predicate | canObserveFrequency |
P76135
|
FINISHED |
| Object | from about 300 MHz to 96 GHz |
—
|
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: from about 300 MHz to 96 GHz | Statement: [Very Long Baseline Array, canObserveFrequency, from about 300 MHz to 96 GHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canObserveFrequency Context triple: [Very Long Baseline Array, canObserveFrequency, from about 300 MHz to 96 GHz]
-
A.
mayObserve
Indicates that one entity is permitted or allowed to observe, monitor, or watch another entity or process.
-
B.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
C.
hasEventFrequency
Indicates how often a particular event occurs within a given time period.
-
D.
hasFrequencyCategory
Indicates that something is associated with a particular classification of how often it occurs or is used.
-
E.
frequencyRequirement
Indicates a constraint specifying how often an action, event, or condition must occur within a given context or time frame.
- F. None of above. chosen
Provenance (4 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_69c6885181008190b419040e22939c7c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb88a2648190acc79eeee8733705 |
completed | March 27, 2026, 8:41 p.m. |
Created at: March 27, 2026, 2:58 p.m.