Triple
T24918225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BS (Broadcasting Satellite) in Japan |
E624046
|
entity |
| Predicate | signalReception |
P157232
|
FINISHED |
| Object | parabolic satellite dish |
—
|
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: parabolic satellite dish | Statement: [BS (Broadcasting Satellite) in Japan, signalReception, parabolic satellite dish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalReception Context triple: [BS (Broadcasting Satellite) in Japan, signalReception, parabolic satellite dish]
-
A.
signalReach
Indicates the extent or range over which a signal can be effectively transmitted or received between entities.
-
B.
signalType
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
C.
signalContent
Indicates that one entity is the informational content or message carried, conveyed, or represented by a signal produced or transmitted by another entity.
-
D.
signalProperty
Indicates that one entity has a specific characteristic, attribute, or feature related to a signal.
-
E.
initialReception
Indicates the nature or quality of the first response or reaction something receives when it is introduced or presented.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4238e43c08190be03e813b8cdfe28 |
completed | May 1, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f423637bec8190a1701421ac86a3b7 |
completed | May 1, 2026, 3:52 a.m. |
Created at: April 18, 2026, 5:28 a.m.