Triple
T16612937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XERB radio broadcasts |
E403621
|
entity |
| Predicate | signalPower |
P48587
|
FINISHED |
| Object | high-powered AM signal |
—
|
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: high-powered AM signal | Statement: [XERB radio broadcasts, signalPower, high-powered AM signal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalPower Context triple: [XERB radio broadcasts, signalPower, high-powered AM signal]
-
A.
signalLevel
chosen
Indicates the intensity or strength of a transmitted or received signal in a communication context.
-
B.
signalProperty
Indicates that one entity has a specific characteristic, attribute, or feature related to a signal.
-
C.
signalVoltage
Indicates the electrical potential level carried by a signal in a circuit or communication channel.
-
D.
signalContent
Indicates that one entity is the informational content or message carried, conveyed, or represented by a signal produced or transmitted by another entity.
-
E.
powerConcentration
Indicates the degree to which authority or control is centralized in a single entity or small group rather than being widely distributed.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3609776d48190b6b8c7826ac575c4 |
completed | April 18, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.