Triple
T35510708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galaxy News Radio |
E1026277
|
entity |
| Predicate | signalStrengthDependsOn |
P183369
|
FINISHED |
| Object | satellite dish condition |
—
|
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: satellite dish condition | Statement: [Galaxy News Radio, signalStrengthDependsOn, satellite dish condition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalStrengthDependsOn Context triple: [Galaxy News Radio, signalStrengthDependsOn, satellite dish condition]
-
A.
signalLevel
Indicates the intensity or strength of a transmitted or received signal in a communication context.
-
B.
estimatedStrength
Indicates that a value represents an approximate or inferred level, magnitude, or intensity of something rather than a precisely measured strength.
-
C.
availableStrength
Indicates the amount of strength or power that an entity currently has ready for use or deployment.
-
D.
signalReach
Indicates the extent or range over which a signal can be effectively transmitted or received between entities.
-
E.
signalReception
Indicates the reception or detection of a transmitted signal by a receiving entity.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:04 p.m.