Triple
T18631958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hughes Syncom communications satellites |
E455438
|
entity |
| Predicate | usedFrequencyBand |
P1685
|
FINISHED |
| Object | microwave 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: microwave band | Statement: [Hughes Syncom communications satellites, usedFrequencyBand, microwave band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedFrequencyBand Context triple: [Hughes Syncom communications satellites, usedFrequencyBand, microwave band]
-
A.
frequencyBand
chosen
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
B.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
C.
frequencyBandSupported
Indicates that an entity supports operation or functionality within a specified frequency band.
-
D.
numberOfFrequencyBands
Indicates the relationship specifying how many distinct frequency bands are associated with or used by an entity.
-
E.
usesFrequencyReuse
Indicates that one entity applies the technique of reusing the same frequency channels across different locations or cells within a system or network.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fc4c5648190b771e9b080e98c15 |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.